Skip to main content

Introduction to the MCP Gateway

Updated on 3 November 2026.

The MCP Gateway sits between your AI apps and the MCP servers they call. Users connect their AI app to a Quilr gateway URL instead of the server itself, and every tool call is checked against your tool rules and guardrails, then logged with the user, the agent and the result.

Your AI app
Claude, ChatGPT, Cursor, VS Code
Connects to a Quilr gateway URL
QuilrAI MCP Gateway
Tool rules and guardrails
Access by agent, group and user
Logs, analytics, health
MCP servers
Remote servers from the MCP Library
Your own servers and APIs
Local packages on the user's computer
QuilrAI

Key concepts​

TermWhat it is
MCP serverThe unit you configure. It holds its connection, sign-in, tools, guardrails and rules. Add one with Add MCP server or from the Library.
Quilr gateway URLThe address agents call for one server, for example https://mcpgateway.quilr.ai/github/mcp. The gateway calls the server's upstream URL.
OneMCPOne URL that serves every MCP a user may use. See OneMCP.
Allowed agentAn AI client, matched by its user-agent keyword. You choose which servers each agent may reach. See Agents Configuration.
User dashboardWhere users sign in at mcpgateway.quilr.ai, connect their accounts and copy their URLs.

New servers start with their tools turned off, so nothing is reachable until you enable it.

The MCP Gateway page​

Go to Settings > AI Gateway > MCP Gateway.

ButtonWhat it opens
Overall analyticsFull-page MCP Gateway Insights, starting on Overview. See Analytics and insights.
OneMCP endpointOneMCP settings. See OneMCP.
Remote connectorsConnectors for private-network MCP servers and REST APIs. See Remote Connectors.
LibraryThe MCP Library. A count shows pending install requests from users.
Tool updatesThe queue of tools added or changed upstream, with the gateway default for new-tool approval. See Tool change watch.
Allowed AgentsWhich AI clients may connect, and which servers each one sees
Add MCP serverThe Add MCP drawer. See Adding MCP Servers.
...Connections (who has connected to which server) and ZIA integration (see Web Search Policy)
Summary tileShows
Tool callsCalls in the period, the share that came through OneMCP, tokens saved and success rate
EstateServers that are Serving, Awaiting connection or have No tools, and how many are enabled or disabled
Tools reachableTools agents can call, with Scoped rules, OAuth servers and the Library queue
Stopped by guardrailsCalls the gateway refused, block rate, failed calls and the previous-period comparison

Click a row on a tile to filter the server list or open the matching view.

BannerAction
N OAuth servers need an administrator connection before their tools can be discovered.Review all filters the list to those servers. With one server, the button reads Connect and the server name.
N quick fixes could prevent failed tool callsReview fixes opens the quick fixes drawer. See Input Aliases.
N servers changed their tools upstream.Review tool updates opens the changes awaiting review. Clients keep the current tool list until the changes are reviewed.

Below the banners, Elsewhere links to Inventory & analytics, the User dashboard and this Documentation. The server list has All, Local, Remote and API tabs, Search servers and a Filter for state, auth, source and runtime.

The server card​

Each configured server has a card.

AreaWhat it shows
HeaderName, System, Library or Local package tag, slug and description
EndpointsQuilr gateway URL (copy it for clients) and the Upstream URL, with upstream p95 and failures
StatusServing, Awaiting connection, No tools found or Disabled, plus transport and auth
ChipsTools, Guardrails, Scoped rules, Token saving, and Tool list once a tool list switch is on (for example Most-used · -91%). Each opens that section.
ActionsShow tools, Uninstall, and the enable toggle
TrafficCalls over time, users, tokens saved, top tools
InspectLogs (the server's activity), Open in Inventory
ConfigureGeneral, API (API servers only), Guardrails, Token Saving, Tool list (remote servers), Tools, Group & User Rules

A server waiting for an administrator OAuth sign-in shows Connect OAuth on its card.

Analytics and insights​

Overall analytics opens a full page with Overview, Usage, Data & security, Reliability, and Servers & tools tabs. Choose the period, server scope and AI-client scope before comparing traffic or following a chart into its details.

See Analytics and insights for adoption, access maps, failure investigation and the difference between tool-list savings and smaller tool results.

The workspace​

The server card's Inspect and Configure actions open operational views. Inspect > Logs opens that server's Activity; Configure opens its settings. These views are separate from full-page Insights. Select the server scope and period in the workspace; Settings needs exactly one server.

TabWhat it shows
ActivityTool calls (one row per call), Interactions (calls grouped into conversations), Findings (guardrail detections)
ConnectionsWhich users have connected to which servers, and their tool calls
HealthGateway verdict, Rejected requests, Access denied, Auth challenges, OAuth refreshes, Upstream server errors, and rejection reasons. Covers the whole gateway.
SettingsThe server configuration. Available for one server at a time.

Settings sections​

Sections vary by server. Edits are drafts until you click Save settings.

SectionWhat you set
GeneralName, connection route, upstream sign-in, custom headers, Access Control, Claims forwarding, Web Search Policy (QuilrAI Web Search only), Uninstall
APIBase URL, connection route, spec and access rules of an API MCP
PermissionsOAuth Permissions: the scopes the connection requests (OAuth servers with selectable scopes)
ToolsTool visibility, Human approval, Tool Change Watch
GuardrailsSecurity Guardrails on tool arguments and tool results
Token savingToken Saving strategies
Tool listTool lists: send the server's most-used tools and keep the rest one search away, optional run_code (remote servers only)
Input aliasesInput Aliases: translate mismatched inputs from AI clients
Group & User RulesGroup & User Rules: overrides for a smart group or a single user
API tokensAPI Tokens for direct connections (not on OAuth servers)
Policy Engine

When the Policy Engine is on, Settings shows Policy Engine active and marks Tools, Guardrails, Token saving, Tool list and Group & User Rules with its icon. Those sections follow published policies instead of these settings. General and API tokens are still managed here.

Next steps​