Skip to main content

MintMCP gateway

Without a gateway, MCP creates problems:

WhoProblem
UsersDon't know which servers to trust, struggle with STDIO setup, overwhelmed by 100+ tools
IT & SecurityCredentials scattered across laptops, unvetted servers, no audit logs
DevelopersOAuth complexity, tool name conflicts, client compatibility issues

MintMCP solves this by providing a single entrypoint that authenticates users, curates tools, and logs everything.

Example

A "Sales Intelligence" Virtual MCP for account executives. Admins curate connectors for CRM, contracts, and communication. Sales reps connect from ChatGPT or Claude, authenticate once through MintMCP, and the gateway controls which connectors they can reach. All usage is logged.

Architecture

MintMCP Gateway Architecture

Request flow

  1. AI client initiates OAuth with MintMCP
  2. MintMCP validates identity, checks policies, returns available tools
  3. Client calls a tool → MintMCP routes to the right connector with credentials
  4. Connector executes, MintMCP logs the call and returns the response

See Core concepts for details.

Components

ComponentWhat it does
AI clientsChatGPT, Claude, Cursor—initiate OAuth and call tools
MintMCP gatewayAuthentication, authorization, routing, logging
Virtual MCPsLogical groupings of connectors exposed as single endpoints
ConnectorsHosted, remote, or STDIO servers that talk to downstream systems
ObservabilityDashboards, audit trails, usage analytics

Governance capabilities

Every request through the gateway is governed:

CapabilityWhat it does
Request loggingRecords every tool call with user, timestamp, and payload
Access policiesControls which users can reach which MCP servers
Credential managementStores secrets centrally instead of on user machines
SSO integrationAuthenticates users through Okta, Google, or Azure AD

These capabilities mean security teams can approve AI tool deployment with full visibility, and compliance teams get the audit trails they need for SOC 2, HIPAA, and internal reporting.