Skip to main content

Remote Connectors

Remote connectors let you register an MCP server that already runs in your infrastructure or is hosted by a vendor. MintMCP treats the remote endpoint as the source of truth while applying gateway-level authentication, authorization, customization, and logging.

When to Use Remote Connectors​

Choose a remote connector when the upstream team already operates the MCP server: for example, SaaS providers that publish their own MCP endpoints (e.g., GitHub's MCP) or internal services that your organization already hosts outside MintMCP.

Authentication Models​

Remote connectors support the credential patterns outlined in Connector Security:

  • Per-user credentials (OAuth or API tokens) keep downstream permissions aligned with the member invoking the tool.
  • Service accounts let administrators share a single token when identical access is sufficient or expected for every member.

MintMCP stores the credentials and brokers them to the remote server while members authenticate with MintMCP using OAuth, ensuring you have per-user attribution for all tool invocations.

Setup Workflow​

  1. Add connector: In the MintMCP console, choose Add Connector and select the remote/server option.
  2. Provide connection details: Supply the remote MCP server URL.
  3. Select authentication: Pick per-user authorization or shared credentials according to the authentication model for the connector.
  4. Bearer tokens: If the connector requires an authorization bearer token, select that option and enter the token.
  5. Click Connect to create the remote MCP connector.
Remote Connector Creation Form

This will attempt to connect to the remote server; if OAuth authorization is required, you'll be guided through the OAuth flow. Credentials will be saved as a service account credential if that option is selected; otherwise, these credentials will be stored under your per-user administrator account only.

Expose through Virtual MCP Servers​

Once MintMCP reports a successful connection to the remote server, you can add the connector to a Virtual MCP server and curate the tool set before sharing it with users (see Virtual MCP Administration and Tool Customization).