MCP

Connect AI assistants to your Suger data and services with the Model Context Protocol (MCP) — an open standard for giving AI agents secure, permissioned access to external tools and data.

The Suger MCP Server lets assistants such as Claude, Cursor, VS Code, and ChatGPT manage your multi-cloud marketplace business in natural language: create and manage offers, entitlements, buyers, and metering; run the co-sell referral lifecycle across AWS, Azure, GCP and Suger partner companies; and manage partner relationships and invitations — all scoped to your organization and your existing Suger permissions.

• Server URL: https://apiv2.suger.cloud/mcp
• Availability: all Suger pricing plans
• Authentication: OAuth 2.1 + PKCE only — no API keys or static tokens
• Access boundary: every tool call is scoped to the authenticated user’s organization and permissions; the server never grants broader access than your Suger account already has

Prerequisites

• A Suger account with the permissions for the actions you want the assistant to take.
• An MCP-capable client (see Supported clients).

Start here

1. Overview — what the server does for an assistant, the kinds of work it takes on, and the security model behind it.
2. Connect an AI Assistant — the per-client setup steps; you need the server URL and an OAuth login, and it takes under a minute.
3. Supported Tools — the full catalog of the 149 tools the server exposes, and what each one covers.

A typical workflow

1. Add the server URL to your client and complete the OAuth login — there’s no key to generate.
2. Ask a question to confirm the connection, e.g. “List my marketplace offers.”
3. Run real tasks in natural language, e.g. “Create a private offer for Acme Corp on AWS with a 20% discount” or “Show entitlements expiring in the next 30 days.” Each result comes back in the conversation.

Supported clients

Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and ChatGPT — plus any client that implements MCP with OAuth 2.1 + PKCE. See Connect an AI Assistant for per-client steps.

Scope and limits

• Tool calls are not rate limited per request — each one is a call to the Suger REST API, which bounds usage with your organization’s service quotas instead.
• The available tool set may change at any time.
• Revenue records, reports, and dashboards aren’t available through the MCP server — use the Revenue workspace in the Suger console.