Documentation

A hosted MCP gateway: aggregate any number of MCP servers and databases behind a single endpoint, add per-user OAuth (bring-your-own-account), governance (RBAC/ABAC, PHI/PII redaction, audit logging) and per-tool config, then connect Claude, Cursor, ChatGPT, or any AI agent.

Get started

Quickstart: connect your MCP gateway

Connect an MCP server, get your single gateway URL, and call your tools from Claude, Cursor, or any agent in under 5 minutes.

Concepts

What is an MCP gateway?

An MCP gateway is a single endpoint that aggregates many MCP servers, adds auth, governance, and audit, and exposes one unified tool catalog to any AI agent.

Per-user OAuth: bring-your-own-account for MCP

Let each end user authorize their own account on a connector. The gateway stores per-user tokens and runs each call as that user - no shared credentials.

Connector auth: shared, per-user, and delegated

How the gateway picks a credential per call: admin-connected vs delegated connectors, and the shared, per-user, and either identity modes.

Multi-tenant agents: one key, many users

Serve many organizations and end users from a single agent using a delegated access key with the X-Org-Id and X-User-Id headers.

Organizations, teams, and roles

Workspaces map to your verified company domain. Learn the owner, admin, member, and viewer roles and your per-org gateway endpoint.

Guides

Connect Claude, Cursor, and ChatGPT

Step-by-step setup for adding your MCP gateway to Claude Desktop, Cursor, ChatGPT, and headless agents via OAuth, bearer token, or config file.

Governance: RBAC, redaction, and per-tool config

Control exactly what agents can do: role-based access, read-only mode, tool exposure, PHI/PII redaction, and per-tool prompt and field rules.

Reference

Gateway API, headers, and access keys

Reference for the /mcp endpoint, authentication headers (Authorization, X-Org-Id, X-User-Id), access keys, and the per-call identity override.

Tools, workflows, and databases

How the gateway names tools, plus composite workflows (one call, many steps) and turning a database into governed MCP tools.

Frequently asked

Do I need to host anything?

No. It is a hosted gateway. You connect MCP servers and get a URL; there is nothing to deploy or run.

Can I connect more than one MCP server?

Yes. The gateway aggregates unlimited MCP servers and databases behind one endpoint and namespaces each tool so calls route to the right server.

What is the Model Context Protocol (MCP)?

MCP is an open protocol that lets AI applications connect to external tools and data sources through a standard interface. An MCP gateway aggregates many such servers behind one endpoint.

How is a gateway different from an iPaaS like Zapier?

An iPaaS runs predefined automations. An MCP gateway exposes live, callable tools to an AI agent at runtime, with per-call identity and governance - the agent decides what to call.

Where are per-user tokens stored?

Encrypted at rest in the gateway vault, keyed to the user's verified identity. Tokens are never returned to the LLM and are refreshed automatically.

Can a user revoke their connection?

Yes. Each user can disconnect any connector from their account, which deletes the stored credential immediately.