Connecting PartnerStack to Claude

Bring your PartnerStack program data into Claude. Once connected, Claude can read your partnerships, customers, leads, deals, transactions, rewards, and links, and (with your explicit confirmation) create or convert records on your behalf.

PartnerStack provides an official remote MCP (Model Context Protocol) server at https://mcp.partnerstack.com/mcp. It exposes the PartnerStack public API as a curated set of tools that Claude can call on your behalf, using your PartnerStack login for authentication.

What you can do with PartnerStack + Claude

  • Pull lists and reports without leaving the conversation. Claude paginates results for you and respects your existing partner-program permissions.
  • Ask questions about your program in natural language. "Show me my top 10 partnerships by created date," "What deals are in stage X with partner Y?", "Which transactions are pending approval?"
  • Create new records with guardrails. Claude will always describe what it is about to create or change and ask for your explicit confirmation before calling write tools.
  • Run saved custom report exports. Trigger and retrieve PartnerStack custom report exports right from the conversation.

Requirements

  • A PartnerStack vendor account with login access to app.partnerstack.com and either Admin or Integration full permissions.
  • One of the following:
    • Claude Desktop (macOS or Windows) — recommended.
    • **Claude.ai web** with a plan that supports custom connectors.
    • Claude Code or any other MCP client that supports remote MCP servers with OAuth.
  • A modern browser (used during the one-time PartnerStack sign-in step).

Note: You do not need an API key. Authentication is handled through your normal PartnerStack login.

Setup

Claude Desktop (recommended)

  1. Open Claude Desktop → Settings → Connectors.
  2. Click Add custom connector.
  3. Set:
    • Name: PartnerStack
    • Remote MCP server URL: https://mcp.partnerstack.com/mcp
  4. Save. Claude will open a browser window to PartnerStack, where you sign in and approve access.
  5. Once you return to Claude, the PartnerStack tools are available in any new conversation.

If your version of Claude Desktop does not yet expose Add custom connector in the UI, you can configure the server directly in claude_desktop_config.json

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

Restart Claude Desktop. A browser window will open the first time a tool is invoked so you can sign in and grant access.

Restart Claude Desktop after saving the file. A browser window will open the first time a tool is invoked so you can sign in and grant access.

💡 Multi-Instance Note: If you have access to multiple instances, you need to select the correct instance on the authorization screen. The PartnerStack MCP only allows connecting to a single instance at a time.

 

mcp-auth (1).png

 

Claude.ai (web)

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

Claude Code (CLI)

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

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

Available tools

All tools are scoped to the PartnerStack account you sign in with and respect the permissions on that account. Tools are grouped by resource.

Partnerships

  • List_all_partnerships — read-only. List partnerships enrolled in your program.
  • Create_a_partnership — Enroll a new partner. Requires explicit user confirmation.
  • Add_partner_member_to_partner_team — Invite or add a member to a partner team.
  • Updates_a_partnerships_tags — destructive. Replace the tag set on a partnership.
  • Retrieve_a_partner_team — read-only. Look up a partner team by its key.

Customers

  • List_all_customers — read-only.
  • Create_a_customer — Create a customer record. Requires confirmation.

Leads

  • List_all_leads — read-only.
  • Create_a_lead — Submit a new lead. Requires confirmation.
  • Convert_a_lead — destructive. Convert a lead into a customer / deal.

Deals

  • List_all_deals — read-only.
  • Get_files_attached_to_a_deal — read-only.
  • Create_a_deal — Create a new deal. Requires confirmation.
  • Assign_partnership_to_deal — Attach a partner to an existing deal.
  • Convert_a_deal — destructive. Convert a deal into a won/customer record.

Transactions

  • List_all_transactions — read-only.
  • Create_a_transaction — Record a transaction. Requires confirmation.

Rewards (Commissions)

  • List_all_rewards — read-only.
  • Create_a_reward — Create a commission. Requires confirmation.

Actions

  • List_all_actions — read-only.
  • Record_action — Record an action event. Requires confirmation.

Groups, links, forms, sales cycles

  • List_all_groups — read-only.
  • List_all_links — read-only. Referral links for a partnership.
  • List_all_form_templates — read-only.
  • Retrieve_Sales_Cycle_Stages — read-only.

Custom Reports

  • list_my_custom_reports — read-only. List your saved custom report configurations.
  • export_custom_report — Trigger an export of a saved custom report.
  • retrieve_custom_report_export — read-only. Fetch the results of an export.

Safety design. Every write tool is annotated so Claude knows it changes data; every destructive tool (Convert_*, Updates_a_partnerships_tags) is annotated as destructive. The MCP server's system prompt instructs Claude to describe the exact change and request your confirmation before any create/update/delete call. Read-only tools (List_*, Get_*, Retrieve_*) do not modify any data.

Security & privacy

  • Encryption in transit. All traffic between Claude and mcp.partnerstack.com runs over HTTPS/TLS. All traffic between the MCP server and PartnerStack's API is internal HTTPS within our managed infrastructure.
  • No vendor data is stored on the MCP server. Responses returned to Claude are not persisted on our side; PartnerStack data lives in its system of record, behind your existing permissions.
  • Tenant isolation. Every request executes under the OAuth token you approved during sign-in. The MCP server cannot read data outside that token's account and scopes.
  • Confirmation before writes. The server's instructions to Claude require explicit user confirmation before any tool that creates, updates, converts, or deletes data is called.
  • Privacy policy. See partnerstack.com/privacy-policy.
  • Terms of service. See partnerstack.com/terms-of-service.

Troubleshooting

Claude keeps asking me to re-authenticate. Quit Claude Desktop, remove the locally cached MCP credentials, and reconnect:

rm -rf ~/.mcp-auth/mcp-remote-*

Then relaunch Claude and re-add the connector. If the problem persists, contact support with the contents of ~/Library/Logs/Claude/mcp-server-partnerstack.log (macOS) or %APPDATA%\\\\Claude\\\\logs\\\\mcp-server-partnerstack.log (Windows).

A tool returned "Not authenticated: no OAuth access token was found." Your PartnerStack session for this connector has expired. Open Claude → Settings → Connectors → PartnerStack → Reconnect.

A list call returned only some results. PartnerStack list endpoints paginate. Tell Claude "continue" or "get the next page" — the MCP server uses cursor pagination, and Claude will pass the cursor value back automatically.

Support

For developer / API issues with the MCP server specifically, please include the request timestamp (UTC) and the conversation ID from Claude so we can correlate against server logs.