PartnerStack is shipping our official remote MCP (Model Context Protocol) server that lets AI assistants read and (with your confirmation) write to your program data: partnerships, customers, leads, deals, transactions, rewards, links, and custom report exports, all in natural language.

💡 One server, two ways to add it. Depending on your AI tool and your license tier, you’ll either add PartnerStack yourself as a custom connector / app, or your IT/workspace admin will need to enable it for you. Each section below tells you which path applies

Before you start: do I need my IT team?

This is the first thing to figure out, because it changes everything downstream.

Connecting to Claude or ChatGPT

Claude

Claude has the most mature, self-serve MCP support. Pick the client you use.

💡 PartnerStack MCP is being reviewed by Anthropic and will be available in the connector directory, meanwhile, the best way to using PartnerStack MCP is via Custom Connector.

Option A — Claude Desktop

1. Open Claude Desktop → Settings → Connectors.
2. Click Add —> Add custom connector.
3. Enter:
   • Name: PartnerStack
   • Remote MCP server URL: https://mcp.partnerstack.com/mcp
4. Save. Claude opens a browser window to PartnerStack — sign in and approve access.
5. Return to Claude. PartnerStack tools are now available in any new conversation.

💡 Multi-instance note: If you have access to multiple PartnerStack instances, select the correct one on the authorization screen (top left). The MCP server connects to one instance at a time. If you picked the wrong instance, disconnect the MCP, and connect again.

If your Claude Desktop doesn’t show “Add custom connector”, you can either ask your IT Admin team to add to your account, or configure the claude_desktop_config.json manually. 

{
  "mcpServers": {
    "partnerstack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "<https://mcp.partnerstack.com/mcp>"
      ]
    }
  }
}

Option B — Claude.ai (web)

1. Go to Settings → Connectors → Browse connectors.
2. Select PartnerStack from the directory — or click Add custom connector and enter https://mcp.partnerstack.com/mcp.
3. Click Connect, sign in to PartnerStack, and approve.

If your Claude Web doesn’t show “Add custom connector”, you can ask your IT Admin team to add to your account.

Option C — Claude Code (CLI)

claude mcp add --transport http partnerstack <https://mcp.partnerstack.com/mcp>

You’ll be walked through the same browser sign-in on first use.

ChatGPT

ChatGPT supports custom MCP servers through Developer Mode. The key fact: the setup differs by plan, and on company plans an admin has to switch it on first.

Eligibility: Developer Mode is available to Plus, Pro, Business, Enterprise, and Education accounts on the web. Free ChatGPT may not support custom connectors.

Step 1 — Enable Developer Mode

If you’re on ChatGPT Plus or Pro (individual):

1. Go to Settings → Apps → Advanced settings.
2. Toggle Developer Mode to ON.
3. Confirm the warning. (Custom connectors are not verified by OpenAI — only add servers you trust. PartnerStack’s is an official first-party server.)

If you’re on ChatGPT Business / Enterprise / Edu (the enablement path differs by plan):

• Business: Only admins/owners can use Developer Mode — regular members can’t enable or use it. If you’re a Business member, your admin will need to set up the connector.
• Enterprise: An admin first grants access under Workspace Settings → Permissions & Roles → Connected Data. Then enabled users turn Developer Mode on themselves via Settings → Apps → Advanced settings. Only admins/owners can publish apps for the workspace, and access can be scoped by role (RBAC).
• 👉 This is your “ask IT” path — send them the URL https://mcp.partnerstack.com/mcp and this section.

Step 2 — Create the PartnerStack app

1. Open ChatGPT → Settings → Apps (Connectors).
2. Next to Advanced settings, click Create app. (This button only appears when Developer Mode is on.)
3. Enter:
   • Name: PartnerStack
   • MCP Server URL: https://mcp.partnerstack.com/mcp
   • Authentication: OAuth
4. Save. The app appears under Drafts in app settings.

Step 3 — Use it in a conversation

1. In a new chat, open the Plus menu → Developer Mode and select the PartnerStack app.
2. The first time you call a tool, ChatGPT opens an OAuth popup — sign in to PartnerStack and approve. (Make sure pop-ups aren’t blocked.)
3. Prompt explicitly for best results, e.g. “Use the PartnerStack app to list my top 10 partnerships by created date.”

Other Agents & MCP Clients

Any MCP-compatible client that supports remote servers with OAuth can connect to PartnerStack. The details are always the same:

Common clients

Cursor
Open Settings → Tools & MCP → New MCP Server (this opens mcp.json), or create the file manually at .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "partnerstack": {
      "url": "<https://mcp.partnerstack.com/mcp>"
    }
  }
}

Cursor triggers the browser OAuth flow on first connect and stores the credentials.

VS Code (GitHub Copilot agent mode) 

Add a .vscode/mcp.json (or via MCP: Add Server):

{
  "servers": {
    "partnerstack": {
      "type": "http",
      "url": "<https://mcp.partnerstack.com/mcp>"
    }
  }
}

Cline / Windsurf / Goose / LibreChat and similar 

Add a remote/HTTP MCP server entry pointing to https://mcp.partnerstack.com/mcp 

Clients that only support local (stdio) servers

Some older or local-only clients can’t talk to a remote HTTPS server directly. Bridge it with mcp-remote:

{
  "mcpServers": {
    "partnerstack": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "<https://mcp.partnerstack.com/mcp>"]
    }
  }
}

This launches a local proxy that forwards to the remote server and handles the browser OAuth flow on first run.

💡 Rule of thumb: if a client asks for a URL, paste the endpoint directly. If it only asks for a command, use the mcp-remote bridge above.

Security & privacy

• Encrypted in transit — all traffic runs over HTTPS/TLS.
• No vendor data stored on the MCP server — responses aren’t persisted; your data stays in PartnerStack’s system of record behind your existing permissions.
• Tenant isolation — every request runs under the OAuth token you approved at sign-in; the server can’t read outside that token’s account and scopes.
• Confirmation before writes — the server instructs the assistant to confirm with you before any create/update/convert/delete.

Policies: partnerstack.com/privacy-policy · partnerstack.com/terms-of-service

Troubleshooting