MCP (Model Context Protocol)
Connect any MCP-compatible server to give Suger AI access to external tools and data.
Overview
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data sources. Suger’s MCP integration lets you connect to any MCP server that supports standard OAuth 2.0 authentication, giving Suger AI the ability to use tools from 75+ popular services --- or any custom MCP server you provide.
Once connected, Suger AI can discover and use all tools exposed by the MCP server. For example, connecting your Stripe MCP server lets Suger AI look up payments, manage subscriptions, and query billing data on your behalf.
Org-Level vs User-Level
Org-Level: Not applicable. MCP server connections are user-level only.
User-Level: Each user connects their own MCP servers with their personal credentials. Tools are available to that user’s Suger AI sessions.
Pre-Configured Providers
Suger includes a catalog of 77 pre-configured MCP servers. Select any provider from the catalog to connect instantly --- no manual URL entry required.
| # | Provider | Category |
|---|---|---|
| 1 | Ahrefs | Marketing |
| 2 | Airtable | Productivity |
| 3 | Apollo.io | Sales |
| 4 | Asana | Project Management |
| 5 | Atlassian (Jira/Confluence/Trello) | Developer Tools |
| 6 | Box | File Storage |
| 7 | Brevo | Marketing |
| 8 | Calendly | Scheduling |
| 9 | Canva | Design |
| 10 | Circleback | Productivity |
| 11 | Clay | Sales & Marketing |
| 12 | Clerk | Developer Tools |
| 13 | ClickUp | Project Management |
| 14 | Close CRM | CRM |
| 15 | Cloudflare | Infrastructure |
| 16 | Cloudflare Developer Platform | Developer Tools |
| 17 | Coda | Productivity |
| 18 | Context7 | Developer Tools |
| 19 | Crossbeam | Partnerships |
| 20 | DevRev | Customer Support |
| 21 | DocuSign | Legal |
| 22 | Dropbox | File Storage |
| 23 | Excalidraw | Design |
| 24 | Fathom | Productivity |
| 25 | Fellow | Productivity |
| 26 | Figma | Design |
| 27 | Fireflies | Productivity |
| 28 | Gamma | Productivity |
| 29 | Granola | Productivity |
| 30 | Guru | Knowledge Management |
| 31 | Honeycomb | Observability |
| 32 | Hugging Face | Developer Tools |
| 33 | incident.io | Incident Management |
| 34 | Intercom | Customer Support |
| 35 | Intuit Mailchimp | Marketing |
| 36 | Intuit QuickBooks | Finance |
| 37 | Klaviyo | Marketing |
| 38 | Linear | Project Management |
| 39 | Lucid | Design |
| 40 | MailerLite | Marketing |
| 41 | Make | Automation |
| 42 | Mermaid Chart | Design |
| 43 | Microsoft 365 | Productivity |
| 44 | Miro | Design |
| 45 | Mixpanel | Analytics |
| 46 | Monday | Project Management |
| 47 | Netlify | Developer Tools |
| 48 | Notion | Productivity |
| 49 | Otter.ai | Productivity |
| 50 | Outreach | Sales |
| 51 | PagerDuty | Incident Management |
| 52 | PandaDoc | Legal |
| 53 | PostHog | Analytics |
| 54 | Postman | Developer Tools |
| 55 | Pylon | Customer Support |
| 56 | Ramp | Finance |
| 57 | Razorpay | Payments |
| 58 | Semrush | Marketing |
| 59 | Sentry | Developer Tools |
| 60 | Shopify | E-commerce |
| 61 | Slack | Communication |
| 62 | Smartsheet | Project Management |
| 63 | Stripe | Payments |
| 64 | Supabase | Developer Tools |
| 65 | Superhuman Mail | Communication |
| 66 | Supermetrics | Analytics |
| 67 | Todoist | Productivity |
| 68 | Twilio | Communication |
| 69 | Typeform | Productivity |
| 70 | Vercel | Developer Tools |
| 71 | Webflow | Developer Tools |
| 72 | Wix | Productivity |
| 73 | WordPress.com | Productivity |
| 74 | Wrike | Project Management |
| 75 | Zapier | Automation |
| 76 | Zoom | Communication |
| 77 | ZoomInfo | Sales |
You can also connect any custom MCP server by entering its URL directly.
Authentication Methods
Suger supports three authentication methods for MCP servers:
| Method | When to use | How it works |
|---|---|---|
| OAuth (PKCE) | Default for most providers | You authorize via the provider’s login page. Suger handles token refresh automatically. |
| Client Credentials | Server-to-server integrations | You provide a Client ID and Client Secret. Suger exchanges them for access tokens and refreshes automatically. |
| API Key | Simple key-based auth | You provide a static API key. No token refresh needed. |
Most catalog providers use OAuth (PKCE) by default. The authentication method is determined by what the MCP server supports.
Create Integration
Connect via Catalog (OAuth)
- Navigate to Settings > Integrations
- Click Connect MCP Server
- Select a provider from the catalog (e.g., Stripe, Linear, Notion)
- You will be redirected to the provider’s authorization page
- Log in and approve access
- You will be redirected back to Suger with status Created
- Click Verify to confirm the connection works
Connect via Custom URL (OAuth)
- Navigate to Settings > Integrations
- Click Connect MCP Server
- Enter your MCP server URL (e.g.,
https://mcp.example.com/mcp) - Suger automatically discovers the server’s OAuth configuration
- Follow the OAuth authorization flow
- Click Verify after returning to Suger
Connect via Client Credentials
- Navigate to Settings > Integrations
- Click Connect MCP Server
- Enter the MCP server URL
- Select Client Credentials as the auth method
- Enter your Client ID and Client Secret
- Click Connect --- Suger exchanges the credentials for an access token
- Click Verify to confirm
Connect via API Key
- Navigate to Settings > Integrations
- Click Connect MCP Server
- Enter the MCP server URL
- Select API Key as the auth method
- Enter your API key
- Click Connect
- Click Verify to confirm
Verification
When you click Verify, Suger probes the MCP server by issuing an initialize request followed by a tools/list request. If the server responds successfully, the integration status changes to Verified and Suger AI can begin using the server’s tools.
Edit Integration
Editing is not supported. Disconnect and reconnect to change credentials or auth method.
Delete Integration
Deleting removes the integration and all stored credentials from Suger.
How It Works
OAuth Discovery
For OAuth-based connections, Suger automatically discovers the provider’s authorization endpoints using open standards:
- RFC 9728 (Protected Resource Metadata) --- determines which authorization server protects the MCP endpoint
- RFC 8414 (Authorization Server Metadata) --- retrieves the authorization, token, and registration endpoints
- RFC 7591 (Dynamic Client Registration) --- registers Suger as an OAuth client if no pre-registered app exists
This means most MCP servers work out of the box without any manual endpoint configuration.
Token Refresh
- OAuth (PKCE): Tokens are refreshed automatically before expiry using the refresh token. If no refresh token was issued, you must reconnect when the token expires.
- Client Credentials: Tokens are refreshed by re-running the client credentials grant --- this is the standard approach per RFC 6749.
- API Key: No refresh needed (static key).
One Connection Per Provider
Each user can have one MCP connection per provider. To switch accounts or credentials, disconnect the existing integration first, then reconnect.
Suger AI Tools
MCP integrations do not provide a fixed set of AI tools. Instead, when you connect an MCP server, Suger AI automatically discovers all tools that the server exposes. The available tools depend entirely on the provider.
For example:
- Stripe MCP might expose tools for querying payments, managing customers, and creating invoices
- Linear MCP might expose tools for creating issues, updating projects, and searching tickets
- Notion MCP might expose tools for reading pages, creating databases, and searching content
The exact tools available are listed during verification and may change as the provider updates their MCP server.