MCP Gateway

Create a single client-facing MCP endpoint that bundles one or more MCP Servers. Clients connect to the MCP Gateway URL and get a unified tool surface without knowing individual server URLs or authentication details. The gateway acts as a virtual MCP server: it aggregates tools from multiple upstream servers behind one address.

This page covers MCP Gateways, client-facing endpoints that bundle upstream MCP Servers Orq connects to. This is a different feature from Orq’s own MCP server, which coding assistants connect to for workspace administration.

Navigate to AI Gateway > MCP Portal in the sidebar. The MCP Gateway tab lists every MCP Gateway in the workspace.

How It Works

A virtual MCP server is a single endpoint that gives clients access to tools from multiple upstream MCP Servers. The gateway aggregates these servers behind one address, handles authentication and routing, and resolves tool-name conflicts internally. Clients connect to one URL and see all linked tools as if they came from one provider.

Use Cases

Exposing multiple MCP servers through a single endpoint for clients that cannot manage multiple connections.
Aliasing server tools under consistent names so clients do not break when upstream tool names change.
Governing tool access per team: admins build an MCP Gateway from a selected subset of tools across several MCP Servers, so the Marketing team and the Research team can share the same servers while reaching different tools.

Set Up an MCP Gateway

Click Create MCP Gateway.

Create MCP Gateway form showing General section with Description and Key, and Tools section with Tool exposure mode and Tool naming — Create MCP Gateway form

Fill in the general details.
- Description (optional): a note about what this MCP Gateway provides.
- Key (required): a unique identifier. Used in the MCP Gateway URL. Cannot be changed after creation.
Configure tool settings.
- Tool exposure mode: how the MCP Gateway presents tools to connected clients. Code mode (default) exposes a single tool provided by the MCP Gateway that handles discovery and execution internally. Direct mode exposes each upstream tool individually.
- Tool naming: how tool names are namespaced across servers. Always prefix with server key (default) prefixes all tools with the server’s key, or its alias if one is set per-link. Prefix on collision only prefixes conflicting names.
Click Create.

After Creation

Orq.ai redirects to the MCP Servers tab of the new MCP Gateway. Click + Add server to link any server already configured in MCP Servers. Only servers that have completed their initial sync can be linked.

Link only MCP Servers whose project access covers the MCP Gateway project access. An MCP Gateway on All projects therefore needs MCP Servers on All projects.

MCP Gateway detail page on the MCP Servers tab listing the tomtom-maps server expanded to show 3 of 18 tools exposed, with Traffic, Alias and Connection panels on the right — MCP Servers tab of an MCP Gateway with a linked server

The MCP Gateway detail page has three tabs:

Overview: traffic for the MCP Gateway and the Connect section with the command clients use to reach it.
MCP Servers: linked servers and the tools each one exposes. Select a tool checkbox to expose it through the MCP Gateway, or clear it to stop exposing it. Both take effect immediately, with no save action. The side panel shows Traffic for the selected server, its Alias (the prefix that namespaces the server’s tools), and its Connection details: server key, type, base URL, auth, and last sync time.
Settings: the MCP Gateway description and tool settings, editable after creation.

Toolsets

Toolsets are named collections of tools from one or more linked servers. Create a toolset from the MCP Gateway detail page by adding tools from linked servers. Attach a toolset to an Agent instead of listing individual tools. When the upstream server adds or removes tools, the toolset picks up the changes on the next sync.

Field	Description
Key	Unique identifier within the project.
Display name	Human-readable label.
Description	What the toolset covers.
Project	The project the toolset belongs to.
Tools	List of server + tool name pairs. Servers must be linked to this MCP Gateway.

Connect a Client

Any MCP-compatible client can reach the MCP Gateway, most often a coding agent such as Claude Code, Cursor, or Codex. See Coding Agents for the full list. The Connect section on the Overview tab holds the command that registers the MCP Gateway with the agent. Set ORQ_API_KEY, then run it.

The examples below use https://my.orq.ai as the default host. For self-hosted or on-premise deployments, replace this with the base URL configured for your deployment. The API’s public_url field returns the full connect endpoint (which may be relative when no public base URL is configured).

Connect section showing an npx add-mcp command with the MCP Gateway URL, a name flag, and an Authorization bearer header — Connect section on the MCP Gateway Overview tab

npx add-mcp https://my.orq.ai/v3/mcp/<gateway-key> \
  --name <gateway-key> \
  --header "Authorization: Bearer $ORQ_API_KEY"

The same endpoint registers in any MCP-compatible client. Common coding agents:

Claude Code
Cursor
Codex
VS Code

claude mcp add --transport http <gateway-key> https://my.orq.ai/v3/mcp/<gateway-key> --header "Authorization: Bearer ${ORQ_API_KEY}"

Replace <gateway-key> with the gateway key from the Connect section and set ORQ_API_KEY to an API key before running the command. Confirm with claude mcp list.

Add the MCP Gateway in Cursor Settings → Tools & MCP → New MCP Server and paste:

{
  "mcpServers": {
    "<gateway-key>": {
      "url": "https://my.orq.ai/v3/mcp/<gateway-key>",
      "headers": {
        "Authorization": "Bearer YOUR_ORQ_API_KEY"
      }
    }
  }
}

Replace <gateway-key> with the gateway key from the Connect section and YOUR_ORQ_API_KEY with an API key. Save the configuration; the server connects and shows a green indicator.

codex mcp add <gateway-key> --url https://my.orq.ai/v3/mcp/<gateway-key> --bearer-token-env-var ORQ_API_KEY

Replace <gateway-key> with the gateway key from the Connect section and export ORQ_API_KEY with an API key in the shell that launches Codex.

Add the MCP Gateway with the MCP: Add Server command, select HTTP (HTTP or Server-Sent Events), and enter https://my.orq.ai/v3/mcp/<gateway-key> as the server URL. VS Code writes a .vscode/mcp.json; replace its contents with:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "orq-api-key",
      "description": "Orq.ai API Key",
      "password": true
    }
  ],
  "servers": {
    "<gateway-key>": {
      "url": "https://my.orq.ai/v3/mcp/<gateway-key>",
      "type": "http",
      "headers": {
        "Authorization": "Bearer ${input:orq-api-key}"
      }
    }
  }
}

Replace <gateway-key> with the gateway key from the Connect section. VS Code prompts for the API key on first connect and stores it in the OS secret store.

Monitor Usage

The Overview tab reports how clients use the MCP Gateway. It opens on the last 7 days, and every card compares that window against the one before it. Change the window with the time range picker in the top right.

MCP Gateway Overview showing Tool calls, Success, Errors and P95 latency cards above a Tool calls by outcome bar chart and a Tools leaderboard of the most called tools — MCP Gateway Overview tab over the last 7 days

Card	Description
Tool calls	Tool invocations routed through the MCP Gateway.
Success	Invocations that completed successfully.
Errors	Invocations that returned an error.
P95 latency	95th percentile duration of successful invocations.

Traffic and reliability breaks the same window down further:

Tool calls by outcome: call volume over time, split into successes and errors.
Tools leaderboard: the most called tools with their call count and P95 latency, listed under their namespaced names.

Audit Changes

Changes to the MCP Gateway are recorded in Audit Logs, so a change to the exposed tool surface can be traced back to whoever made it. Entries are written under two entity types:

Entity type	Recorded when
MCP Gateway	A gateway is created, updated, or deleted, including changes to its linked servers.
MCP Server	A server is created, updated, or deleted.

Filter by either entity type on the Audit Logs page to see only MCP Portal activity.

Overview

APIs

MCP Portal

Routing

Security & Privacy

Model Capabilities

Common Scenarios

How It Works

Use Cases

Set Up an MCP Gateway

After Creation

Toolsets

Connect a Client

Monitor Usage

Audit Changes

​How It Works

​Use Cases

​Set Up an MCP Gateway

​After Creation

​Toolsets

​Connect a Client

​Monitor Usage

​Audit Changes

How It Works

Use Cases

Set Up an MCP Gateway

After Creation

Toolsets

Connect a Client

Monitor Usage

Audit Changes