Connect Patch to AI assistants (MCP)

What is MCP?

Model Context Protocol (MCP) is an open standard that lets AI models connect to external tools and data sources. Instead of copying data into a chat window, the AI calls Patch directly — with your permission.

Patch MCP is a remote connector. Add it once to your AI client, sign in with your Patch account, and the assistant can use Patch data in conversation.

Before you start

You'll need:

1. An MCP-compatible AI client — ChatGPT, Claude, Cursor, Codex, or MCP Inspector.
2. A Patch account with the permissions you want the AI to use.
3. The Patch MCP endpoint:

Connect your AI client

Every client uses the same endpoint and OAuth flow. Steps differ slightly by product.

Claude

1. Click here to auto configure all your Claude Patch MCP settings.

2. Click Continue.
3. Complete Sign in with Patch when prompted.

Alternative:

1. Open Claude → Settings → Connectors.
2. Click Add connector → Custom connector.
3. Enter the name and URL from the table above.
4. Leave advanced settings blank. Clicking "Connect" will redirect you to sign in with your Patch account (OAuth) — no client ID, secret, or token needed.

ChatGPT

1. Open ChatGPT → Settings → Connectors (or Apps & Connectors).
2. Click Add connector → Custom / Remote MCP.
3. Enter the name and URL from the table above.
4. Complete Sign in with Patch when prompted.

Requires a paid ChatGPT plan with custom connector support.

Claude Desktop

Add to claude_desktop_config.json and restart:

{  "mcpServers": {     
     "patch": {       
       "command": "npx",       
       "args": [         
          "mcp-remote",         
          "https://mcp.patchretention.com/mcp"       
        ]     
      }   
   } 
}

On first use, complete the OAuth flow in your browser.

Cursor

Option A — Settings UI (recommended)

1. Open Cursor → Settings → MCP.
2. Add a remote server named patchpointing at https://mcp.patchretention.com/mcp.
3. Authenticate on first data use. Clicking "Connect" will redirect you to sign in with your Patch account (OAuth) — no client ID, secret, or token needed.

Option B — Project config

Add to .cursor/mcp.json:

{  "mcpServers": {     
      "patch": {       
        "url": "https://mcp.patchretention.com/mcp"     
      }   
   } 
}

Codex

1. Open your Codex environment → MCP Servers or Connectors.
2. Add a remote server with the URL. 
3. Clicking "Connect" will redirect you to sign in with your Patch account (OAuth) — no client ID, secret, or token needed.

If your environment expects stdio servers, use the mcp-remote bridge (same config as Claude Desktop above).

Sign in with Patch

Regardless of client:

1. The AI client redirects you to Patch's authorization page.
2. Sign in with your Patch credentials.
3. Select the account you want the AI to access.
4. Approve the connection.

Your Patch credentials are never shared with the AI provider. The MCP server verifies your token with Patch's session API and delegates data calls through Patch's security layer.

To switch accounts, disconnect the connector and reconnect through OAuth.

Verify it's working

Start a new conversation and try:

• "What Patch data do you have access to?"
• "How many contacts are in my account?"
• "Show me my recent blasts."
• "List my automations."

The AI should call Patch MCP data and return live data from your account.

What can Patch MCP do?

Patch MCP exposes data from the Patch Agents platform. Ask naturally — you don't need to memorize data names.

Data categories

What MCP cannot do

• Access data from accounts you don't belong to
• Bypass Patch permissions or approval requirements
• Auto-approve write actions without your consent

Getting help

If you still can't connect after trying the steps above:

1. Note the error message and which AI client you're using.
2. Check whether the issue is auth, data discovery, or tool execution.
3. Contact your Patch rep with the details.