Skip to main content

Hosted Connectors

Hosted connectors run MCP servers inside MintMCP's managed infrastructure. Instead of asking members to execute npx or pip commands locally, administrators supply the standard configuration once and the gateway provides a stable, governed endpoint.

When Hosted Connectors Make Sense​

  • You find an open-source MCP server and want to roll it out to your organization without asking every user to manage the runtime.
  • You need to centralize secrets or environment variables that should never live on developer laptops.
  • You need audit logging and observability for how the MCP server is used.
  • You prefer to let MintMCP handle scaling, restarts, and container lifecycle for lightweight stdio services.

See Enable OAuth for STDIO Servers for an end-to-end walkthrough of hosting a STDIO-based MCP server on MintMCP.

Deploy Through the UI​

  1. Navigate to MCP Connectors in the MintMCP console and choose Add Connector.
  2. Select the Hosted Server option.
  3. Paste the MCP "Standard Config" JSON for your stdio server, including command, arguments, and any required environment variables.
  4. Save the connector to trigger deployment. MintMCP launches the server in a managed container and reports status once it boots.
Add Hosted Connector

Example: Supabase STDIO Server​

{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": [
        "-y",
        "@supabase/mcp-server-supabase",
        "--read-only",
        "--project-ref=<project-ref>"
      ],
      "env": {
        "SUPABASE_ACCESS_TOKEN": "<access-token>"
      }
    }
  }
}

Remember to replace any required configuration values with your own values before deploying.

MintMCP encrypts stored environment variables by default. After deployment you can monitor revisions, logs, and tool definitions directly from the connector detail page.

See Enable OAuth for STDIO Servers for an end-to-end walkthrough of hosting a STDIO-based MCP server on MintMCP.

Ongoing Management​

  • Review connector logs if a hosted server fails to start; typical issues mirror local development (missing env vars, invalid command flags).
  • When the upstream project releases updates, modify the config and redeploy. MintMCP tracks revisions so you can see how the server has changed over iterations.
  • Use VMCP Tool Customization to curate tools before exposing the hosted connector broadly.

Next Steps​

  • Add the hosted connector to one or more Virtual MCP servers and decide who should have access.
  • Share the Virtual MCP URL with members so they can follow the User Guide.
  • For advanced automation, explore the CLI workflow described in Custom MCP Connectors.