OneMCP
Updated on 3 November 2026.
OneMCP exposes the MCPs a user is allowed to access through one endpoint. Agents can discover MCP groups, find relevant tools, call tools, manage per-user connections, and use native memory tools without configuring each service as a separate MCP server.
To steer Claude, ChatGPT, or GitHub Copilot to use the discovery flow reliably, see Agent Custom Instructions for copy-paste text and ready-to-use files.
OneMCP handles remote services and does not choose a computer automatically. To run an administrator-approved Python or Node MCP on a user's own machine, with the same gateway access checks, see Local MCP.
What a user does with this endpoint: copy it, add it to Claude, ChatGPT or Cursor, and check which tools they are allowed to call.
YouTube All videosEndpoint
Replace <YOUR_MCP_BASE_URL> in the examples with your deployment's HTTPS base URL, without a trailing slash. This can be https://mcpgateway.quilr.ai, https://mcpgateway.quilrai.com, or another exact hostname assigned under quilrai.com. Copy the base from your Quilr dashboard; the placeholder includes https://.
The OneMCP URL is:
<YOUR_MCP_BASE_URL>/quilrone/mcp
For example, if your base is https://mcpgateway.quilrai.com, use https://mcpgateway.quilrai.com/quilrone/mcp.
Quilr resolves the organization from the signed-in account and applies that user's connector and tool permissions.
OneMCP accepts gateway-issued OneMCP OAuth proxy tokens, which the AI client gets when the user signs in. There is no token to copy. For quick examples see Connect an AI client. Administrators should use the detailed AI client setup guides, including Copilot Studio, GitHub Copilot, Claude, Cursor, ChatGPT, and Codex.
OneMCP settings
Choose the instructions for the mode that governs your MCP Gateway. See Switching from classic settings for what happens to stored settings when the engine is on.
- Classic settings
- Policy Engine
Go to Settings > AI Gateway > MCP Gateway and click OneMCP endpoint.
Changes save as soon as you select them.
OneMCP policy settings
Open Govern > Policy Engine > MCP Gateway > Controls > OneMCP Features.
Choose a recipe or blank rule in a section, set Applies to and the outcome, check Reads as, and Save to draft. Use Test for the intended caller and a caller outside the scope, then review and publish.
The Activity tab shows observed matches. Server tool-list pins remain managed in server settings; see Tool lists.
Smart Tools
When dynamic tool calling is on, OneMCP returns a compact set of gateway tools:
When an administrator turns on tool lists for a server, its most-used tools are also listed directly, named <server-slug>_<tool> (for example crm_search_records), and run_code is added when a server allows scripts. Tool lists are off by default, so without them the list is just the tools above.
The usual flow is:
- Call
find_relevant_toolswith a short task description. - Call
call_toolwith the selected tool name and arguments. - If the user asks to view, connect, authenticate, or reconnect MCPs, call
list_mcp_connections.
Native Memory Tools
OneMCP includes native memory tools for user-scoped context. Their availability follows the classic Memories enabled setting or the matching OneMCP memory policy described in OneMCP settings.
Memory records are scoped to the current user. Each memory can include:
Example:
{
"title": "Preferred CRM account",
"content": "Use Acme Corp's enterprise account when creating sales reports.",
"tags": ["crm", "sales"],
"source": "user"
}
Inline Authentication
OneMCP keeps policy-accessible MCPs visible before the current user has connected them. It can guide the user through an upstream OAuth flow or collection of a required per-user API key without making the user leave their AI workflow to find the right MCP settings.
In-Chat Connector Card
MCP Apps-compatible clients, including ChatGPT, can render an Available connectors card directly in the conversation. Ask the client to show available connectors, connect an MCP, or reconnect an MCP. OneMCP routes that request to list_mcp_connections and attaches the card.
The card provides:
- Connection needed and Connected tabs.
- Connect or Reconnect actions for each MCP that needs user authentication.
- Connection-status checks after the user returns from the provider flow.
- A Manage connectors action that opens the user dashboard for adding or requesting MCPs.
Connection links remain private to the connector card in UI-capable sessions. Other OneMCP tools direct the client to list_mcp_connections when authentication is needed.
Clients Without the Connector Card
- Clients that support URL elicitation can show the connection flow in a host-provided prompt.
- Other clients receive the existing tool error and short-lived connection-link guidance.
After authorization, retry the original request. For OAuth MCPs, the gateway stores and refreshes the upstream token for that user. Per-user API keys are also stored against that user's upstream connection.
Visibility Rules
OneMCP shows MCPs that are available to the user by organization policy, user preferences, and agent access controls. It does not include OAuth passthrough MCPs, because passthrough clients must manage the upstream OAuth flow and provide the upstream bearer token directly to the per-MCP endpoint.
Operational Notes
- Connect URLs are short-lived and should be treated as sensitive links.
- If a connect link expires, ask the client to refresh the connector list before trying again.
- If an OAuth MCP requires manual client credentials and none are configured, the connect flow cannot complete until an admin adds those credentials.
- Basic clients use stateless
POSTJSON-RPC requests. Clients that negotiate the richer OneMCP session capabilities can also use the supported event stream and session termination methods.