Run and deploy an exported MCP server

Start with the generated README

Download and unzip the generated project, inspect its source and follow its README for the chosen runtime. TypeScript exports use the MCP TypeScript SDK; Python exports use FastMCP. Installation instructions depend on the selected runtime, package manager and transport.

The web app performs bounded structural validation. It does not spawn build or test processes for uploaded projects. Run the generated project's tests and build locally; the mcpmint CLI and repository verification workflow provide local full verification where supported.

Choose a transport and access policy

Use stdio when an MCP client launches the server as a local process. Use Streamable HTTP or SSE when running a separately hosted service and configure the client for that transport. The Export installation wizard provides connection configuration for supported clients.

For HTTP or SSE, bind to localhost during development. Before exposing a network listener, configure MCP bearer access with MCP_AUTH_TOKEN and appropriate allowed origins. Generated servers deny non-localhost Origin headers by default when the allow-list is empty. Origin checks complement authentication; they do not replace it.

Configure upstream authentication separately using the generated environment template. Keep secret values out of NEXT_PUBLIC_ variables, specifications, portable project files and source control. Deploy behind HTTPS and apply upstream request permissions suitable for the selected tools.

Verify before connecting an agent

Inspect the outgoing request with the browser sandbox, run mocks and test real requests locally against a development API. Review schema conversion warnings, authentication selection and state-changing methods. Use the least privilege possible and monitor the deployed server.

If you deploy the mcpmint website itself, set NEXT_PUBLIC_SITE_URL to the actual HTTPS origin before building. The website uses server API routes and security headers, so it requires a Next.js server or compatible platform; it is not a pure static export. The repository deployment verification guide covers crawler access and search indexing checks.