Overview
Connect AI assistants to your Fours data & services using natural language.
The Fours 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 Fours pricing plans
MCP Server URL: https://api.suger.cloud/mcp
How it fits together
Your assistant never talks to the Fours 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 Fours API under your own organization and permissions.
The catalog is derived from the Fours 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.
- 234 tools: Cover the public Fours API, your revenue records, receivables, payouts and credit memos, your analytics data with its saved charts and dashboards, and your funding applications, integrations and workflow runs — from creating offers to running the full co-sell referral lifecycle across AWS, Azure, GCP and Fours partner companies, to running your partner program: partners, invitations, journeys, tasks, training, agreements, events, shared files and the program’s settings. The tool list may change at any time.
- No deletes by default: An assistant you connect yourself gets none of the
DELETEendpoints by default, so it cannot delete a Fours record. Deletes stay with people, in the Console and the REST API. Fours AI, the assistant in the Fours Console, can be given them through the Access setting on its own connection to this server (see MCP).
Get Started
Most people are connected and running their first prompt in under a minute:
- Add the Fours MCP Server to your client using the server URL above.
- Sign in and approve access when your browser opens — there’s no API key to generate.
- 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 Fours MCP Server
Connect your AI assistant to Fours 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 Fours 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 Fours.
- “Who are our partners, and what has Contoso earned?” — Look up partner relationships, contacts and commission ledgers, and send or answer partnership invitations.
- “Which partners are stuck in onboarding?” — Find stalled partner journeys and overdue steps, and see how partners are doing on your training courses.
- “Which AWS lead invitations haven’t we accepted yet?” — List the leads AWS Partner Central sent you and accept the ones you want.
- “What was our total AWS revenue from July through September?” — Total your revenue records for a period without exporting them.
- “Which AWS invoices are more than 90 days overdue?” — List your open receivables, payouts and credit memos from chat.
- “Chart our revenue by marketplace for the last 12 months and save it” — Query your analytics data, and save charts and dashboards for your team.
- “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
| Category | Examples | Tools |
|---|---|---|
| Organization | List organizations, check enabled services and quotas, track Get Started onboarding | 5 |
| Products & Offers | Create, publish, sync, and manage marketplace listings | 32 |
| Entitlements | Approve, cancel, schedule renewals, manage terms and pricing | 23 |
| Buyers & Contacts | Manage buyer records, credit wallets, link contacts | 19 |
| Metering & Usage | Report usage, manage billable metrics, validate records | 14 |
| Reports | Daily usage-metering records from the cloud marketplaces, and daily revenue records | 2 |
| Revenue | Query your revenue records and total them for a period; list your receivables invoices, payouts, credit memos and each marketplace’s raw billing rows | 6 |
| Analytics | Query your analytics data — revenue, AWS billing events, offers, entitlements, products, buyers, co-sell referrals and leads — and read, build and change saved charts and dashboards | 21 |
| Co-Sell | Run the referral lifecycle across AWS, Azure, GCP and Fours partner companies; register a deal on a partner’s behalf; manage partner commissions on Fours co-sells; review and fill in deal-registration drafts; list and accept AWS leads; ask AWS which funding programs a referral qualifies for; look up Azure solution ids; search partner connections | 35 |
| Funding | Your AWS benefit wallets — each program’s balance, status and expiry — and your funding applications: list and read them, prefill one from a CRM opportunity, check it, save it as a draft, and submit it once a person approves | 8 |
| Partner Management | Partner relationships, contacts and commission ledgers; partnership invitations; journeys, tasks and partner training; agreements, events and shared files; the program dashboard; program settings and tiers | 40 |
| Support | Create, update, and resolve support tickets, and download their files | 11 |
| Notifications | Notification events, messages, and org-level config | 6 |
| Operations & Auditing | Track operations and audit events | 4 |
| Integrations | List your connected integrations, read one, and run its verification checks | 3 |
| Workflow runs | Find your workflow runs and read what each one produced | 3 |
| API Management | List and inspect API clients | 2 |
Your revenue records, receivables invoices, payouts and credit memos are available through the Revenue and Reports tools, and the Analytics tools can query and chart your revenue. The Revenue workspace’s own dashboards and financial reports aren’t tools — use the Revenue workspace in the Fours console for those.
For the complete tool reference, see Supported Tools. For co-sell-specific workflows and troubleshooting, see Run Co-Sell Workflows with Fours MCP. For partner-management workflows, the permission each PRM tool needs and worked examples, see Partner Management with AI (MCP).
Supported Clients
You can connect to the Fours MCP Server from popular AI assistants and code editors, including:
- Claude Desktop
- Claude Code
- Cursor
- VS Code (GitHub Copilot)
- Devin Desktop (formerly Windsurf)
- ChatGPT
You can also build custom applications that connect to the Fours MCP Server. Any client that implements the MCP specification with OAuth 2.1 + PKCE (Proof Key for Code Exchange) is supported. A client that supports dynamic client registration registers itself the first time it connects, so there is nothing to request from Fours. If yours can’t register itself, contact Fours support.
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 Fours 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 Fours REST API, which bounds usage with your organization’s service quotas rather than a request rate — the same rule as for direct API calls.
Analytics queries are the exception. Fours runs only so many at once for your organization, so in a
burst a query waits briefly and is then refused as busy (BUSY); try again in a moment. A query
that would read too much data is refused with COST_TOO_HIGH until it is narrowed. See
Supported Tools.
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? It can still connect if it implements the MCP specification with OAuth 2.1 + PKCE. A client that supports dynamic client registration registers itself the first time it connects. If yours can’t, contact Fours support.
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.
Spotted something wrong or out of date on this page? Tell us and we'll correct it.