What Is the Summit53 MCP Server?
The Summit53 MCP (Model Context Protocol) Server lets you connect your CRM data directly to AI assistants like Claude, ChatGPT, Cursor, Windsurf, and any MCP-compatible client. Once connected, you can ask natural-language questions about your pipeline, accounts, forecasts, and deals β and get answers grounded in real CRM data.
Summit53 exposes 14 read-only tools across six categories: Search, Account Intelligence, Pipeline & Risk, Forecasting, Activity, and Research. All connections use OAuth 2.0 authentication and scoped tokens so your data stays secure.
https://api.summit53.io/mcp/Prerequisites
- An active Summit53 account with organization admin access
- Access to the MCP integration page at
/admin/integrations/mcp - For Claude Desktop / Cursor / Windsurf: Node.js v18+ installed locally
- For Claude.ai or ChatGPT: A Pro, Team, or Enterprise subscription that supports connectors
Option 1: Connect to Claude.ai
Claude.ai supports MCP connectors natively through its Settings panel. This is the quickest setup path β no local software required.
Steps
- Open claude.ai/settings/connectors (or go to Settings β Connectors in the Claude sidebar).
- Click "Add custom connector" at the bottom of the connectors list.
- Enter the following details:
- Name: Summit53
- URL:
https://api.summit53.io/mcp
- Click Save, then click Configure next to the new Summit53 connector.
- You will be redirected to Summit53 to authorize via OAuth. Sign in with your Summit53 credentials and grant access.
- Once authorized, the connector status will show as configured. You can now use Summit53 tools in any Claude conversation.
Option 2: Connect to ChatGPT
ChatGPT supports MCP connectors through its Apps settings. The Summit53 connector uses OAuth for secure authentication.
Steps
- Open chatgpt.com and click on your profile icon, then Settings.
- Navigate to Apps in the settings sidebar.
- Click "Add app" or "Connect" and search for Summit53, or add it manually using the MCP server URL:
- URL:
https://api.summit53.io/mcp
- URL:
- Authorize Summit53 via OAuth when prompted. Sign in with your Summit53 account credentials.
- Once connected, Summit53 will appear in your Apps list showing the connection details:
- Authorization: OAuth
- Actions: All 14 Summit53 tools will be listed
Preferences
In the ChatGPT connector settings, you can toggle "Reference memories and chats" to allow ChatGPT to reference relevant previous conversations when querying Summit53 data. This is off by default for privacy.
Option 3: Connect to Claude Desktop
Claude Desktop connects to Summit53 via the mcp-remote proxy, which bridges the local stdio-based MCP protocol to the remote Summit53 server.
Steps
- Install mcp-remote (one-time):
npx mcp-remote https://api.summit53.io/mcp/This will download and cache the mcp-remote package. You can also install it globally with
npm install -g mcp-remote. - Add to Claude Desktop config. Open your
claude_desktop_config.jsonfile and add Summit53 undermcpServers:{ "mcpServers": { "summit53": { "command": "npx", "args": [ "mcp-remote", "https://api.summit53.io/mcp/" ] } } }The config file location depends on your OS:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
- macOS:
- Restart Claude Desktop to pick up the new server configuration.
- Authorize. When you first use a Summit53 tool, a browser window will open prompting you to sign in and authorize the MCP client to access your CRM data.
Option 4: Other MCP Clients (Cursor, Windsurf, Codex)
Any MCP-compatible client can connect to Summit53 using the same mcp-remote proxy pattern. The general approach is:
- Add a new MCP server entry in your clientβs configuration.
- Set the command to
npx mcp-remote https://api.summit53.io/mcp/ - Authorize via OAuth when prompted on first use.
For Cursor, add the server in Settings β MCP. For Windsurf, add it in the MCP configuration panel. For Codex, configure via the CLI settings.
Token Management
After connecting a client, you can manage active tokens from the Summit53 MCP admin page at /admin/integrations/mcp.
Token Scopes
Each token is issued with the following read-only scopes:
| Scope | Description |
|---|---|
crm:read | Search and read accounts, contacts, and opportunities |
pipeline:read | Access pipeline risk analysis and deal heatmaps |
revenue:read | Read forecast data, ARR metrics, and revenue narratives |
actions:read | Retrieve weekly action plans and activity gap reports |
Revoking Access
To disconnect a client, click "Revoke All" next to the client name in the Connected Clients list. This immediately invalidates all tokens for that client. The client will need to re-authorize to regain access.
Rate Limits
The MCP server enforces rate limits to ensure fair usage across your organization:
| Limit | Value |
|---|---|
| Global (per organization) | 100 requests / minute |
| Per tool (default) | 30 requests / minute |
| Window | 60 seconds (rolling) |
Some tools have lower limits due to computational cost:
| Tool | Override Limit |
|---|---|
external_account_research | 10 / minute |
arr_growth_narrative | 15 / minute |
weekly_action_plan | 15 / minute |
Monitoring Usage
The Activity tab on the MCP admin page provides real-time usage monitoring. You can view Total Calls, Total Errors, and a Tool Usage Breakdown across 1-hour, 6-hour, 24-hour, and 7-day windows. Use this to track adoption across your team and identify any issues.
Troubleshooting
Connection fails during OAuth
Ensure you are signing in with an account that has admin access to your Summit53 organization. If using Claude Desktop, check that Node.js v18+ is installed and npx is available in your PATH.
Tools not appearing after connection
For Claude Desktop, restart the application after editing claude_desktop_config.json. For Claude.ai, try refreshing the page or starting a new conversation. For ChatGPT, click "Refresh" in the connector information panel.
Rate limit errors
If you encounter rate limit errors, wait 60 seconds before retrying. If your team consistently hits limits, contact Summit53 support to discuss higher quotas.
Token expired
Tokens expire after one year. If your connection stops working, check the Active Tokens table on the MCP admin page for expiration dates. Reconnect the client to issue a new token.
Next Steps
- MCP User Guide β Learn how to use Summit53 tools in your daily workflow
- MCP Tool Reference β Detailed documentation for all 14 available tools
- Integrations Overview β Connect Salesforce, Google Workspace, and other data sources