Skip to main content

Add a hosted connector

Run MCP servers inside MintMCP's managed infrastructure—instead of asking members to execute npx or pip commands locally, you supply the configuration once and MintMCP handles the rest.

When to use hosted connectors​

  • You want to roll out an open-source MCP server without asking every user to manage the runtime
  • You need to centralize secrets or environment variables that shouldn't 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

Adding a hosted connector​

  1. Navigate to MCP store in the MCP gateway sidebar
  2. Click + Add MCP
  3. Select Add Hosted Connector
Add Hosted Connector form with JSON configuration

Configuration steps​

  1. Find the JSON config for your STDIO MCP server (docs often call it "Standard config")
  2. Paste the JSON in the text box
  3. Replace placeholders with your actual values (e.g., API keys)
  4. Click Create

Example configuration​

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-fetch"]
    }
  }
}

Environment variables​

MintMCP encrypts stored environment variables, which you specify in the env section:

{
  "mcpServers": {
    "my-server": {
      "command": "npx",
      "args": ["-y", "@example/mcp-server"],
      "env": {
        "API_KEY": "your-api-key"
      }
    }
  }
}

For servers that depend on private npm packages, see Using private npm packages in hosted servers.