MCP Servers

• Name: the server key, with the provider logo when the server comes from a pre-configured provider
• Description: the description entered at creation
• Access: which projects can use the server
• Last update: when the server last changed
• Created by: the workspace member who added it

​

Use Cases

• Connecting third-party SaaS tools (Slack, Linear, Figma, etc.) to agents without writing custom integrations.
• Exposing internal APIs as callable tools for agents.
• Centralizing MCP server management instead of configuring connections per tool or per agent.
• Sharing a single MCP server across multiple agents and gateways with controlled tool exposure.

​

How It Works

​

Set Up an MCP Server

1. Click MCP Server.

2. Pick a provider or enter a custom URL. The MCP Provider dropdown lists pre-configured providers (Airtable, Slack, Linear, and more). Selecting one pre-fills the connection details and authentication headers. Choose Custom to enter a server URL manually.
3. Fill in the general details.
   • Key (required): a unique identifier for this server. Used in tool name prefixes when linked to a gateway.
   • Description (optional): a note about what this server provides.
4. Set the connection.
   • Type: HTTP (default) or SSE for streaming-capable servers.
   • URL (required): the endpoint of the upstream MCP server.
5. Configure authentication.
   • None (default): for public servers that require no credentials.
   • Static Headers: send fixed headers with every request. Header values are stored encrypted and never returned by the API. A {{variable}} placeholder keeps a value out of storage: the server stores only the name, and the value is supplied when the server is tested, synced, or a tool is called. Placeholder values are not persisted. A server with template variables cannot be used in an MCP gateway.
   • OAuth Client Credentials: authenticate with an upstream OAuth 2.0 authorization server using the client credentials grant. Fill in the Client ID, Client Secret, and Token URL (the endpoint that issues tokens, for example https://accounts.example.com/oauth/token). The client secret is stored securely and never returned in API responses. See How OAuth Client Credentials works. This credential is distinct from the OAuth flow MCP clients use to connect to a gateway.
   • Enterprise managed: call the server through an MCP Gateway on behalf of each SSO user. Enable Cross App Access first, then enter the server’s authorization settings. See Enterprise-managed authorization.
6. Test the connection. Click Test connection to probe the server before saving. For Enterprise managed, this checks authorization discovery without requesting a user token or listing tools. Other authentication types validate the connection and return discovered tools.
7. Click Create.

​

How OAuth Client Credentials works

​

Enterprise-managed authorization

​

Troubleshoot enterprise-managed authorization

​

After Creation

• View discovered tools in the Tool Sets tab. Select a tool to see its description, arguments, and input schema. The sync state shows the total tool count, tools added and removed since the last sync, the last synced timestamp, and any sync errors. This tab is the browser for the tools this server exposes.
• Control tool exposure when the server is linked to a gateway: select the tool checkboxes on the gateway’s MCP Servers tab (see MCP Gateways). Exposure also accepts a read-only filter in the API. It keeps only the tools the upstream server annotates as read-only (readOnlyHint). The gateway trusts that annotation and does not check what the tool does.
• Test a tool by filling in the arguments and clicking Run tool. The test invokes the tool on the upstream server and shows the response.
• Re-sync to pick up changes from the upstream server. New tools are added, removed tools are dropped.
• Configure project access in the Settings tab. Under Access control, pick All projects to share the server with the whole workspace, or Custom and set each project to Enabled or Disabled. A gateway can only link servers whose project access covers it.
• Duplicate a server to create a copy with the same connection and tool settings under a new key.

​

Delete a Server

curl -X PATCH https://my.orq.ai/v2/mcp-gateways/<gateway-id> \
  -H "Authorization: Bearer $ORQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "server_links": [
      {
        "mcp_server_id": "mcp_server_01JQ0K5R8N2ZC7X4M9T3V6HWBD",
        "alias": "weather",
        "tool_exposure": { "mode": "MCP_TOOL_EXPOSURE_MODE_ALL" }
      }
    ]
  }'

import { Orq } from "@orq-ai/node";

const client = new Orq({
  apiKey: process.env.ORQ_API_KEY ?? "",
});

await client.mcpGateways.update({
  id: "mcp_gateway_01HZXW2K7Y8Q9M0N1P2R3S4T5V",
  updateMcpGatewayRequest: {
    serverLinks: [
      {
        mcpServerId: "mcp_server_01JQ0K5R8N2ZC7X4M9T3V6HWBD",
        alias: "weather",
        toolExposure: { mode: "MCP_TOOL_EXPOSURE_MODE_ALL" },
      },
    ],
  },
});

import os
from orq_ai_sdk import Orq

client = Orq(api_key=os.environ["ORQ_API_KEY"])

client.mcp_gateways.update(
    id="mcp_gateway_01HZXW2K7Y8Q9M0N1P2R3S4T5V",
    server_links=[
        {
            "mcp_server_id": "mcp_server_01JQ0K5R8N2ZC7X4M9T3V6HWBD",
            "alias": "weather",
            "tool_exposure": {"mode": "MCP_TOOL_EXPOSURE_MODE_ALL"},
        }
    ],
)

curl -X DELETE https://my.orq.ai/v2/mcp-servers/<server-id> \
  -H "Authorization: Bearer $ORQ_API_KEY"

import { Orq } from "@orq-ai/node";

const client = new Orq({
  apiKey: process.env.ORQ_API_KEY,
});

await client.mcpServers.delete({
  id: "mcp_server_01JQ0K5R8N2ZC7X4M9T3V6HWBD",
});

import os
from orq_ai_sdk import Orq

client = Orq(api_key=os.environ["ORQ_API_KEY"])

client.mcp_servers.delete(id="mcp_server_01JQ0K5R8N2ZC7X4M9T3V6HWBD")

​

Monitor Usage

​

Attach to an Agent

​

Attach to a Gateway