Works with

One MCP server for Claude, ChatGPT, Claude Code, Cursor and Copilot

Add ContextGate once, as a connector or an MCP server. Every tool call your AI app makes through it is checked against your workspace's policies and logged.

Create a free workspace first, then follow the steps for your app.

Claude connectors: add ContextGate as a custom connector · Web, desktop app and Cowork

  1. In Claude, open Settings → Connectors and click Add custom connector.

  2. Name it ContextGate and paste this URL:

    https://api.contextgate.ai/mcp
  3. Click Add, then Connect, and sign in to ContextGate.

  4. In a chat, turn ContextGate on from the + menu → Connectors. Cowork and the desktop app use the same connectors.

On Team and Enterprise plans an Owner first adds the connector under Admin settings → Connectors, then each member clicks Connect. Free plans allow one custom connector.

Claude's own instructions

ChatGPT connectors: add the ContextGate MCP server in developer mode · Developer mode connectors

  1. In ChatGPT settings, open Apps & Connectors (or Connectors) → Advanced and turn on Developer mode.

  2. Create a connector, choose OAuth, and paste this URL:

    https://api.contextgate.ai/mcp
  3. Sign in to ContextGate when ChatGPT redirects you, then pick the connector in a chat.

Developer mode is a beta on paid ChatGPT plans. On Business, Enterprise and Edu an admin turns it on for the workspace. OpenAI moves these settings from time to time.

ChatGPT's own instructions

Microsoft Copilot MCP: add ContextGate to a Copilot Studio agent · Copilot Studio agents

  1. In Copilot Studio, open your agent's Tools page and select Add a tool → New tool → Model Context Protocol.

  2. Enter ContextGate as the Server name, a short Server description, and this Server URL:

    https://api.contextgate.ai/mcp
  3. Under authentication choose OAuth 2.0 with Dynamic discovery, then select Create.

  4. On Add tool, select Create a new connection, sign in to ContextGate when asked, then select Add to agent.

If sign-in doesn't start, choose API key instead: type Query, parameter name api_key, and a key from API keys in your ContextGate workspace. A data policy on Power Platform connectors also applies to MCP servers. These steps follow Microsoft's documentation, and Microsoft moves these settings from time to time.

Microsoft Copilot's own instructions

Claude Code MCP: add the ContextGate MCP server with one command · Terminal and IDE

  1. Run this in a terminal:

    claude mcp add --transport http contextgate https://api.contextgate.ai/mcp
  2. Start Claude Code, run /mcp, choose contextgate and sign in to ContextGate.

Claude Code's own instructions

Cursor MCP: one-click install of the ContextGate MCP server · One-click install

Add to Cursor
  1. Click Add to Cursor, or add this to ~/.cursor/mcp.json:

    {
      "mcpServers": {
        "contextgate": {
          "url": "https://api.contextgate.ai/mcp"
        }
      }
    }
  2. In Cursor Settings → MCP, sign in to ContextGate when Cursor asks.

Cursor's own instructions

VS Code and GitHub Copilot MCP: add ContextGate in agent mode · In VS Code, agent mode

Add to VS Code
  1. Click Add to VS Code, or add this to .vscode/mcp.json:

    {
      "servers": {
        "contextgate": {
          "type": "http",
          "url": "https://api.contextgate.ai/mcp"
        }
      }
    }
  2. Start the server when VS Code asks, sign in to ContextGate, and use it from Copilot Chat in Agent mode.

GitHub Copilot's own instructions

Codex MCP: add ContextGate to OpenAI's coding agent · OpenAI's coding agent

  1. Run this in a terminal:

    codex mcp add contextgate --url https://api.contextgate.ai/mcp
  2. Then sign in to ContextGate:

    codex mcp login contextgate

Codex's own instructions

Gemini CLI MCP: add ContextGate to Google's terminal agent · Google's terminal agent

  1. Run this in a terminal:

    gemini mcp add --transport http contextgate https://api.contextgate.ai/mcp
  2. In Gemini CLI, run /mcp auth contextgate and sign in to ContextGate.

Gemini CLI's own instructions

Any MCP app: add the ContextGate MCP server URL · Any app that supports MCP

  1. Add a remote (HTTP) MCP server with this URL:

    https://api.contextgate.ai/mcp
  2. Apps that support MCP sign-in ask you to sign in to ContextGate the first time they connect.

  3. An app that can't sign in can use a workspace API key instead: create one under API keys and add ?api_key=<your key> to the URL.

Every app above uses the same URL, https://api.contextgate.ai/mcp. Once your AI app is connected, ask it to use one of your connected apps through ContextGate, then open Activity in your workspace to see the call. Writing code? The developer guide covers Claude Code, Cursor and VS Code in more depth.

Questions people ask

Is there one MCP server that gives Claude, ChatGPT and Cursor the same company context?

Yes. Add ContextGate once to each AI app as a connector or MCP server, using the same URL. Claude, ChatGPT, Cursor, Claude Code, Copilot and the other apps on this page then reach the same connected company apps through that one connection, under the same tool switches and policies, instead of each app needing its own connector for every tool.

Do I have to set up each company app again in every AI app?

No. You connect your company apps (a CRM, a ticketing tool, a drive) to your ContextGate workspace once. Every AI app you add to ContextGate sees the same tools, so adding a new AI app is one connection, not a new set of keys and settings.

What is checked when an AI app calls a tool through ContextGate?

Every tool call is checked against your workspace policies, which can block it, warn on it or redact personal data in the result, and only tools you have switched on are visible. Each call is then recorded in Activity with the user, the AI app, the tool, its arguments and the policy outcome.

Is this an MCP gateway?

Yes. An MCP gateway is one MCP server that your AI apps connect to, which sits in front of the real servers and tools. ContextGate is an MCP gateway: one connection for every AI app, with credentials held in the workspace, a switch for each tool, policies on every call and one activity log.

New to the idea? What is an MCP gateway? explains how one works. Securing the servers behind it? MCP security best practices covers the ten controls to apply, or create a free workspace.