Connect an AI Assistant

Set up Suger MCP Server in your preferred AI assistant or code editor.

This guide walks you through connecting the Suger MCP Server to your preferred AI assistant or code editor. Setup takes under a minute — you just need the server URL and an OAuth login.

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

Prerequisites

• A Suger account on any pricing plan
• An AI assistant or code editor that supports the Model Context Protocol (MCP)

Claude

Claude Desktop

1. Open Settings and go to Customize > Connectors
2. Click Add custom connector
3. Enter the following:
   • Name: Suger
   • Remote MCP server URL: https://apiv2.suger.cloud/mcp
4. Click Add, then complete the OAuth login when prompted

Custom connectors are available on every plan (Free is limited to one connector).

Claude Desktop (config file)

If you’d rather configure the server through a local config file:

1. Open Claude Desktop settings > Developer > Edit Config
2. Add the following to claude_desktop_config.json:

{
  "mcpServers": {
    "suger": {
 "url": "https://apiv2.suger.cloud/mcp"
    }
  }
}

3. Restart Claude Desktop

Claude Code

claude mcp add --transport http suger https://apiv2.suger.cloud/mcp

Then run /mcp within a Claude Code session to complete authentication.

Cursor

Open Cursor Settings > MCP > Add new MCP server, then enter:

• Name: Suger
• Type: HTTP
• URL: https://apiv2.suger.cloud/mcp

Alternatively, add this to .cursor/mcp.json:

{
  "mcpServers": {
    "suger": {
 "url": "https://apiv2.suger.cloud/mcp"
    }
  }
}

VS Code (GitHub Copilot)

Run in your terminal:

code --add-mcp '{"type":"http","name":"suger","url":"https://apiv2.suger.cloud/mcp"}'

Then open the MCP panel in VS Code and start the Suger server.

Windsurf

Open Settings (Ctrl+, / Cmd+,) > MCP Servers, then add:

{
  "mcpServers": {
    "suger": {
 "serverUrl": "https://apiv2.suger.cloud/mcp"
    }
  }
}

ChatGPT

1. Go to Settings > Apps
2. Search for Suger
3. Click Connect and authorize access to your Suger workspace

Other Clients

Any MCP-compatible client can connect. Use the standard configuration:

{
  "mcpServers": {
    "suger": {
 "url": "https://apiv2.suger.cloud/mcp"
    }
  }
}

If your client doesn’t support remote MCP servers natively, use mcp-remote as a bridge:

npx -y mcp-remote https://apiv2.suger.cloud/mcp

Sign in and approve access

The first time a client connects, it opens Suger in your browser. You sign in, choose what the assistant can reach, and the browser hands you back to the client. The steps are the same for every client above.

1. Sign in. Suger’s sign-in page opens at console.suger.io. Click Log In — or, if your organization uses single sign-on, the SSO to button that carries your organization’s name. If this browser is already signed in to the Suger console, you skip this step: the page shows Redirecting… and moves straight on.

   An SSO to button appears for each single-sign-on organization you have opened in the Suger console in this browser. If yours isn’t listed, sign in to the Suger console with SSO first (see Okta SSO), then connect the client again.

2. Check the account. The Authorize Application screen names the client asking for access and shows the account you’re signed in as, under Authorizing as. If that’s the wrong account, see Use another account.

3. Choose access for each organization. Every organization you belong to is listed, each with three choices:

   Choice	What the assistant can do in that organization
   All	Whatever your role allows, checked on every request — if your role changes, so does the assistant’s access
   Custom	Only the permissions you select, and never more than your role allows. Up to three organizations can use Custom
   Off	Nothing — the assistant can’t reach that organization

4. Click Allow. Your browser returns to the client, which is now connected. Deny cancels the connection.

Use another account

Use another account on the Authorize Application screen signs this browser out of Suger — including the Suger console — and shows the sign-in page, so you can sign in as someone else. You then come back to Authorize Application as that account.

Verify Your Connection

After setup, try a few prompts to confirm everything is working:

"List my marketplace offers"
"Show recent entitlements"
"How many active buyers do I have?"

If the connection is successful, your assistant will prompt you to authenticate (first time only), then return live data from your Suger workspace.

Troubleshooting

Authentication fails

• Ensure your Suger account has the required permissions for the operations you’re attempting
• Confirm your MCP client supports OAuth 2.1 with PKCE
• Try disconnecting and reconnecting the integration

Signed in as the wrong account

• On the Authorize Application screen, click Use another account and sign in again — see Use another account

Your organization uses single sign-on

• On the Suger sign-in page, choose the SSO to button for your organization
• If it isn’t listed, sign in to the Suger console with SSO in the same browser, then reconnect the client

Tools not appearing

• Double-check the server URL is exactly https://apiv2.suger.cloud/mcp
• Restart your MCP client after any configuration change
• Verify network connectivity to apiv2.suger.cloud

Rate limit errors

• Tool calls are not rate limited per request; a rate limit error while connecting comes from the sign-in (OAuth) endpoints, which limit attempts per minute. Wait a minute, then reconnect
• A tool that creates resources can reach one of your organization’s service quotas — request an increase there
• Contact Suger support if the errors persist