Co-Sell with AI (MCP)

Run the full co-sell referral lifecycle from your AI assistant, using natural language

Overview

The Suger MCP Server exposes Suger’s co-sell APIs as tools that any Model Context Protocol client — Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, ChatGPT — can call. Instead of clicking through the Suger Console, a Partner or Alliance Manager can describe what they want in plain language and let the assistant create referrals, look up status, sync with the cloud partner, and read dashboard insights.

One connection covers AWS, Azure, and GCP co-sell, plus peer-to-peer co-sell with the partner companies you work with through Suger. The destination is chosen per call by the partner field: AWS / AZURE / GCP share the opportunity with that cloud provider, and SUGER shares it with another company you partner with through Suger.

Availability: All Suger pricing plans

MCP Server URL: https://apiv2.suger.cloud/mcp

See MCP → Setup to connect your client, and MCP → Overview for the full tool catalog and security model.

Prerequisite: your organization’s co-sell integration must already be connected — see Co-Sell Configuration.

Co-Sell tools

The MCP server exposes 13 co-sell tools, covering the whole referral lifecycle:

Suger peer-to-peer referrals (partner=SUGER)

A SUGER referral is shared with another company you partner with through Suger, not with a cloud provider. It behaves differently in three ways worth knowing before you prompt for one:

• The partner responds in Suger. The recipient gets their own copy in PENDING_ACCEPTANCE. They accept by moving it to ACTIVE, or decline by setting status to REJECTED with a declineReason (required — the request is refused without it). Only the company that received the referral can respond; the sender withdraws instead. Both use UpdateCosellReferral.
• No outbound sync is needed. There is no external partner system to push to — Suger keeps the partner’s copy in step itself. SyncSingleReferral on a SUGER referral synchronizes the linked CRM record, accepts direction=OUTBOUND only, and returns an error for INBOUND.
• Send only the fields you are changing. On a partner’s copy whose deal value is hidden, a read returns dealValueAmount, dealValueCurrency and sharePercentage blanked out. Reading a referral and sending the whole object back writes those blanks or fails validation — so ask the assistant to patch specific fields rather than echo a record back.

Use ListPrmPartners (see MCP → Supported Tools) to find the partner and get the partnerId a SUGER referral needs.

Example prompts

• List: “List my AWS referrals in Pending Acceptance status from last week.”
• Detail: “Show me referral ref-abc123.”
• Create: “Create an AWS co-sell referral for Acme Corp, expected close date 2026-09-30.”
• Validate first: “Validate this referral against the AWS schema before I submit it.”
• Update status / stage: “Move referral ref-abc123 from Draft to Submitted.”
• Sync: “Sync referral ref-abc123 outbound to AWS.”
• Insights: “Show my co-sell pipeline for the last 30 days.”
• Partner lookup: “Who at AWS have we worked with for acme.com before?”
• Share with a partner company: “Share the Acme deal with Contoso as a Suger co-sell referral.”
• Respond to a partner: “Accept the referral Contoso shared with us.”

Recommended workflow

1. Validate before you create. Ask the assistant to run ValidateReferral first — each cloud partner requires different fields, and a dry run surfaces missing values before anything is sent.
2. Create the referral. On a successful create the referral is submitted to the partner automatically; its status becomes PENDING_CREATE (or CREATE_FAILED if the partner API rejects it — fix the fields and re-create). If your organization has the co-sell approval process enabled, a brand-new referral is instead saved as DRAFT and is not submitted until it is approved in the Suger Console.
3. Track and update. Use ListCosellReferrals / GetCosellReferral to check progress, and UpdateCosellReferral to edit fields or move status / stage.
4. Sync when needed. For AWS / Azure / GCP, UpdateCosellReferral changes Suger only; call SyncSingleReferral afterwards to push the change to the cloud partner or pull the latest partner state. A SUGER referral needs no such call — Suger propagates the partner’s copy itself, and SyncSingleReferral there syncs the linked CRM record instead.

Security & scope

• Authentication: OAuth 2.1 only (API keys and static tokens are not supported for MCP).
• Organization scoping: every tool call is scoped to your authenticated organization — there is no way to reach another organization’s referrals.
• Permissions: the MCP server respects your existing Suger co-sell permissions (read / create / edit). It never grants access broader than your account already has.

Troubleshooting

FAQ

Can I manage co-sell funding requests through MCP? No — funding applications are managed in the Suger Console and API only. See Co-Sell Funding.

Can my AI assistant delete a referral or sync my whole organization at once? No. Destructive and org-wide operations are intentionally excluded from MCP tools. Use the Suger Console for these.

What happens right after I create a referral? It submits to the cloud partner automatically and its status becomes PENDING_CREATE (or CREATE_FAILED if the partner rejects it — fix the fields and re-create). If your organization has co-sell approval enabled, it is saved as DRAFT until approved in the Console instead.

Does updating a referral in chat also update it with the cloud partner? Not automatically. UpdateCosellReferral only changes the Suger record — call SyncSingleReferral afterwards to push the change to the partner. This applies to AWS, Azure and GCP; a SUGER referral has no external partner system, and Suger keeps the partner’s copy in step itself.

Can I share a deal with another Suger partner company, not a cloud provider? Yes — create the referral with partner=SUGER and the partnership’s partnerId. The partner receives their own copy and accepts or declines it in Suger. See Suger peer-to-peer referrals above.

For the developer view of the same create endpoint, see Create a Referral via API.