Overview

Connect AI assistants to your Suger data & services using natural language.

The Suger MCP Server lets AI agents and assistants work directly with your cloud marketplace data. Ask questions in natural language, automate repetitive tasks, and manage your multi-cloud business — all from the AI tools you already use.

It implements the Model Context Protocol (MCP), the open standard for connecting AI assistants to external data sources and actions.

Availability: All Suger pricing plans

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

How it fits together

Your assistant never talks to the Suger API directly. The MCP server tells your client which authorization server to use; your client runs the OAuth 2.1 + PKCE sign-in itself and holds the token. From then on it attaches that token to every call, and the server forwards each request to the Suger API under your own organization and permissions.

The catalog is derived from the Suger API itself rather than maintained by hand, which is why it tracks the API and why the tool list can change at any time.

Key Features

• Multi-cloud marketplace management: Manage products, offers, entitlements, and buyers across AWS, Azure, and GCP Marketplace from a single interface.
• OAuth 2.1 authentication: Secure, token-based access scoped to your organization. Your AI assistant can only perform actions you have permission to do.
• 149 tools: Cover the public Suger API — from creating offers to running the full co-sell referral lifecycle across AWS, Azure, GCP and Suger partner companies, to managing partner relationships and invitations. The tool list may change at any time.
• No deletes: Every DELETE endpoint is excluded from the tool catalog, so an assistant cannot delete a Suger record. Deletes stay with people, in the Console and the REST API.

Get Started

Most people are connected and running their first prompt in under a minute:

1. Add the Suger MCP Server to your client using the server URL above.
2. Sign in and approve access when your browser opens — there’s no API key to generate.
3. Ask something simple to confirm the connection, like “List my marketplace offers.”

For exact steps by client (Claude Desktop, Cursor, VS Code, and others), see Connect an AI Assistant.

Scenarios for Using the Suger MCP Server

Connect your AI assistant to Suger MCP and use natural language for tasks like:

• “Create a private offer for Acme Corp on AWS with a 20% discount” — Draft and manage offers without switching to the Suger console.
• “Show me all entitlements expiring in the next 30 days” — Get instant visibility into upcoming renewals.
• “Share this opportunity to AWS as a co-sell referral” — Run the full referral lifecycle (create, validate, sync, status updates) for AWS / Azure / GCP from chat, or share the deal with a partner company through Suger.
• “Who are our partners, and what has Contoso earned?” — Look up partner relationships, contacts and commission ledgers, and send or answer partnership invitations.
• “Report usage for entitlement ent-123” — Submit metering data directly from your development environment.
• “What support tickets are open right now?” — Triage and update tickets from your editor.

What You Can Do

Revenue records, reports, and dashboards aren’t available through the MCP server — use the Revenue workspace in the Suger console.

For the complete tool reference, see Supported Tools. For co-sell-specific workflows and troubleshooting, see Run Co-Sell Workflows with Suger MCP.

Supported Clients

You can connect to the Suger MCP Server from popular AI assistants and code editors, including:

• Claude Desktop
• Claude Code
• Cursor
• VS Code (GitHub Copilot)
• Windsurf
• ChatGPT

You can also build custom applications that connect to the Suger MCP Server. Any client that implements the MCP specification with OAuth 2.1 + PKCE (Proof Key for Code Exchange) is supported. Contact Suger support to register your client.

Security and Access Control

• Authentication: OAuth 2.1 only. API keys and static tokens are not supported.
• Organization scoping: Every tool call is scoped to the authenticated user’s organization, ensuring complete data isolation.
• Permission model: The MCP server respects your existing Suger permissions — it never grants broader access than what your account already has.

Rate Limiting

Tool calls are not rate limited per request. Each tool call is a call to the Suger REST API, which bounds usage with your organization’s service quotas rather than a request rate — the same rule as for direct API calls.

The sign-in (OAuth) endpoints are the exception: they limit attempts per minute, so connecting or reconnecting a client many times in quick succession can be refused. Wait a minute, then try again.

Frequently Asked Questions

Can I use API keys instead of OAuth? No. OAuth 2.1 is the only supported authentication method, ensuring secure, organization-scoped access.

Does this support write operations? Yes. You can create offers, manage entitlements, report usage, run co-sell workflows, and more — not just read data. All write operations respect your account permissions.

What happens if my MCP client isn’t on the supported list? Contact Suger support. We can evaluate and register your client as long as it implements the MCP specification with OAuth 2.1 + PKCE.

How is data isolated between organizations? The OAuth token determines your organization scope. All queries and mutations are restricted to your organization’s data — there is no way to access another organization’s resources through the MCP server.