Drive the PartnerSignals Portal from your AI assistant.
Connect Claude, ChatGPT, Cursor, Codex, or VS Code to the portal over MCP. Register deals, log partner motions, and pull enablement content — from the assistant you already use.
https://eco.partnersignals.ai/mcpEnterprise-grade governance by design. Every connection is admin-approved, OAuth 2.1 authorization-code, and scoped by row-level security. Your assistant only ever sees what you would see in the portal.
Quickstart
Connect in under a minute.
Pick your client. One-click install where the client supports it — copy-paste config everywhere else.
Claude Desktop & Claude Code
For Claude Code, run the CLI. For Claude Desktop, add the JSON block to claude_desktop_config.json.
claude mcp add --transport http partnersignals https://eco.partnersignals.ai/mcp{
"mcpServers": {
"partnersignals": {
"type": "http",
"url": "https://eco.partnersignals.ai/mcp"
}
}
}Cursor
Deep-link install, or add manually to ~/.cursor/mcp.json.
{
"mcpServers": {
"partnersignals": {
"url": "https://eco.partnersignals.ai/mcp"
}
}
}VS Code (GitHub Copilot)
Deep-link install (VS Code 1.99+), or add manually to your workspace .vscode/mcp.json.
{
"servers": {
"partnersignals": {
"type": "http",
"url": "https://eco.partnersignals.ai/mcp"
}
}
}Codex & ChatGPT
For Codex CLI, add to ~/.codex/config.toml. For ChatGPT, add a custom connector in Settings → Connectors pointing at the endpoint above and complete the OAuth prompt in your browser.
[mcp_servers.partnersignals]
type = "http"
url = "https://eco.partnersignals.ai/mcp"Or call it directly
Paste an OAuth access token you obtained via the authorization-code flow and fire a raw JSON-RPC request. Great for smoke-testing your integration.
curl -X POST https://eco.partnersignals.ai/mcp \
-H "Authorization: Bearer YOUR_OAUTH_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "list_partner_motions",
"arguments": { "category": "Deal Execution" }
}
}'How it works
Approval process
Agent access is a manual, admin-gated grant — not an automatic self-service switch. That's the trust story: partner data stays inside a governed perimeter, and every AI connection has a real person's sign-off behind it.
- 01
Apply to the Signals Partner Program
Submit your company details on the Become a Partner page.
- 02
Get approved as a partner
Our team reviews your application, typically within two business days.
- 03
Request MCP access
Tick the request-agent-access box on the application, or ask your partner admin.
- 04
We enable access
A PartnerSignals administrator manually enables agent access on your account — reviewed for every request.
Tools
What your assistant can do.
Eight tools cover the day-to-day partner workflow — from deal registration to content search. Every tool runs as you, scoped by RLS.
Create Deal Reg
register_deal"Register a new deal for Acme Corp, $150k ARR, closing March 2026, on AWS, with a Marketplace Co-Sell motion."
List My Deals
list_my_deals"Show me all my open deal registrations."
Get Deal Detail
get_deal"What's the status of my Acme Corp deal reg?"
List Partner Motions
list_partner_motions"What partner motions are available for the account-planning stage?"
List Motion Categories
list_partner_motion_categories"What are the top-level partner motion categories?"
Submit Partner Motion
submit_partner_motion"Log a Joint Account Plan motion for the Acme Corp account."
Search Content
search_content"Find me the latest co-sell playbook."
List Announcements
list_announcements"Any new partner program announcements?"
Motion catalog
Partner motions are grouped into six top-level buckets across the customer lifecycle.
Field Engagement
Pre-opportunity
Sales Alignment
Pre / cross-opportunity
Account Planning
Opportunity opens
Deal Execution
Opportunity → close · MEDDPICC-governed
- Prove the Fit
- Engage the Customer
- Build & Present the Proposal
- Close the Deal
Ecosystem & Marketplace
Pre-opportunity sourcing
Post-Sale & Lifecycle
Post-close
The full catalog is always current via list_partner_motions — ask your assistant to list motions for any category or stage.
Security & governance
Enterprise controls, not enterprise friction.
RLS-scoped
Row-level security enforces that no partner ever sees another partner's deals, motions, or content. The tool runs as you.
Every call audited
Tool name, arguments, success/failure, and duration are logged and visible to PartnerSignals administrators.
Admin-revocable
An administrator can revoke agent access at any time; the next tool call from that assistant fails immediately.
OAuth 2.1 authorization-code
Browser-based consent flow with dynamic client registration. We deliberately do not support password-grant tokens — the interactive consent step is the security boundary.
Try it
Example prompts.
Once connected, paste any of these into your assistant.
"Register a new deal for Acme Corp, $150k ARR, closing March 2026, on AWS, with a Marketplace Co-Sell motion."
register_deal·Live"Show me all my open deal registrations."
list_my_deals·Live"What's the status of my Acme Corp deal reg?"
get_deal·Live"What partner motions are available for the account-planning stage?"
list_partner_motions·Live"What are the top-level partner motion categories?"
list_partner_motion_categories·Live"Log a Joint Account Plan motion for the Acme Corp account."
submit_partner_motion·Live"Find me the latest co-sell playbook."
search_content·Live"Any new partner program announcements?"
list_announcements·LiveFAQ
Common questions.
Why doesn't a password-grant token work?
The PartnerSignals MCP server only accepts tokens minted through the OAuth 2.1 authorization-code flow — the one that opens a browser tab, asks you to sign in, and shows a consent screen naming the client requesting access. Password-grant would let a script hold your credentials and mint tokens with no interactive consent, which defeats the audit and revocation model. There is no scripted shortcut around the browser step by design.
How long does approval take?
Partner applications are typically reviewed within two business days. MCP access is a separate, manual grant by an administrator once you're an approved partner — request it on the application form or ask your partner admin. We do not auto-approve.
What data can an assistant see?
Exactly what you can see in the portal. Every tool call runs as your user, and Supabase row-level security enforces per-partner scoping — no assistant can read another partner's deals, motions, or content.
Can I revoke access?
Yes — an administrator can revoke agent access on your account at any time from the admin console. The next tool call from any connected assistant fails immediately.
Does the assistant store my access token?
The token lives inside your assistant's local credential store. PartnerSignals never sees or stores it. Disconnecting the MCP server in your assistant removes it locally; revoking on the server side invalidates it globally.
Which MCP clients are confirmed compatible?
Claude Desktop, Claude Code, ChatGPT (via custom connectors), Cursor, Codex, and VS Code (with GitHub Copilot). Any client that speaks MCP Streamable HTTP + OAuth 2.1 should work.
Docs & support
Go deeper.
Full guides live in the partner content library (sign-in required — consistent with the approval-gated model). The public manifest is open for technical inspection before you connect.
MCP User Guide
End-to-end walkthrough for partner users connecting an AI assistant.
OpenSign-in required
MCP Administrator Guide
Architecture, access control, auditing, and incident response for administrators.
OpenAdmin sign-in required
Public MCP Manifest
Machine-readable tool catalog. Inspect the exposed tools, arguments, and annotations before connecting.
View JSONOpen · no auth