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. The cloud is chosen per call by the partner field (AWS / AZURE / GCP).

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 11 co-sell tools, covering the whole referral lifecycle:

Tool	What it does
`ListCosellReferrals`	List referrals (inbound + outbound) with filters — partner, status, stage, time range, text
`GetCosellReferral`	Get the full record for one referral by ID
`CreateCosellReferral`	Create an outbound referral to a cloud partner (AWS / AZURE / GCP)
`UpdateCosellReferral`	Edit referral fields, status, or stage
`BatchCreateCosellReferrals`	Create several referrals in one call (recommended ≤ 20)
`ValidateReferral`	Dry-run validate a referral against the partner schema before creating it
`SyncSingleReferral`	Sync one referral inbound or outbound with the cloud partner
`AzureInvitePartnerCollaboration`	Invite another partner to collaborate on an Azure referral (Azure only)
`GetCosellDashboard`	Co-sell insights — pipeline KPIs, outstanding actions, activity logs
`GetPartnerContacts`	List known partner contacts for a buyer company (by email domain)
`SearchPartnerConnections`	Search the org’s connected AWS partners by name

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?”

Recommended workflow

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.
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.
Track and update. Use ListCosellReferrals / GetCosellReferral to check progress, and UpdateCosellReferral to edit fields or move status / stage.
Sync when needed. UpdateCosellReferral changes Suger only; call SyncSingleReferral afterwards to push the change to the cloud partner or pull the latest partner state.

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.

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