MCP Integration: Setup Guide

What Is the Summit53 MCP Server?

The Summit53 MCP (Model Context Protocol) Server brings the Summit53 Revenue Engine into compatible AI assistants. It lets your team diagnose what is happening, decide the next best action, execute permitted workflows, and preserve value evidence around the Figure-Eight revenue loop — using live Summit53 and CRM context rather than generic model knowledge.

The server registers 116 functions across 18 categories: Search, Opportunity Strategy, Revenue Loop, Account Intelligence, Customer Success, Pipeline & Risk, RevOps, Forecasting, Activity, Research, Notes & Activities, Outreach, Value Impact, Coaching, Meetings, Knowledge Base, Job Lifecycle, and Discovery. It also publishes read-only prompts, resources and interactive apps. The functions a client actually sees depend on its granted scopes, the user’s Summit53 permissions and whether the connection is eligible for action approvals. Use list_available_tools to see the current session’s list. The in-product Ask Summit53 assistant is a separate, read-only surface and does not mirror the external catalogue.

Interactive clients use OAuth with PKCE, so everyone signs in with their own Summit53 account and no API key is needed. Approved service integrations may use scoped static API keys, but API keys are not part of the normal setup described below.

Recommended: The Summit53 Plugin for Claude and Codex

The Summit53 plugin installs the connector and the Summit53 skills in one step. Skills are guided workflows that turn the raw functions into finished work: a weekly forecast-movement brief, a manager deal review, a board revenue pack, a renewal defence, a coaching 1:1 deck, a territory review and more. Every skill checks which organisation it is connected to before reading any data and reports missing evidence as unavailable rather than zero. The plugin is published at github.com/Summit53/skills and works in Claude (claude.ai, Claude Desktop, Cowork and Claude Code) and in Codex.

If you only want the functions, without the guided workflows, add the connector on its own using the options below.

Prerequisites

• An active Summit53 account that is an approved member of your organisation
• Access to the MCP integration page at /admin/integrations/mcp
• For Claude.ai or ChatGPT: a plan that supports custom connectors or apps
• Only for clients that cannot connect to a remote server directly: Node.js v18+ installed locally, for the mcp-remote bridge

Option 1: Connect to Claude.ai, Claude Desktop or Cowork

Claude supports remote MCP connectors natively. No local software is required, and Claude Desktop uses the same connectors as claude.ai, so connecting in either one is enough.

With the Summit53 plugin (recommended)

1. Open Customize → Plugins → Add and add the marketplace https://github.com/Summit53/skills.
2. Install Summit53.
3. Open the plugin’s Connectors tab, connect Summit53 and sign in with your Summit53 account.

Plugins installed in claude.ai also sync into Claude Code.

Connector only

1. Open claude.ai/settings/connectors (or go to Settings → Connectors in the Claude sidebar).
2. Click "Add custom connector" at the bottom of the connectors list.
3. Enter the following details:
   • Name: Summit53
   • URL: https://api.summit53.io/mcp
4. Click Save, then click Configure next to the new Summit53 connector.
5. You will be redirected to Summit53 to authorise via OAuth. Sign in with your Summit53 credentials; you are returned to Claude once the connection is authorised.
6. Once authorized, the connector status will show as configured. You can now use Summit53 tools in any Claude conversation.

Rolling out to a Team or Enterprise organisation

A Claude organisation Owner can make Summit53 available to everyone: add the connector under Organization settings → Connectors, then add the Summit53/skills marketplace under Organization settings → Plugins & skills and set the Summit53 plugin to Installed by default or Required. Each member still signs in with their own Summit53 account, so every answer stays scoped to what that person is allowed to see.

Option 2: Connect to Claude Code

With the Summit53 plugin (recommended)

/plugin marketplace add Summit53/skills
/plugin install summit53@summit53
/reload-plugins

Connector only

claude mcp add --transport http summit53 https://api.summit53.io/mcp

Either way, run /mcp, select summit53, choose Authenticate and complete the browser sign-in.

Option 3: Connect to Codex

With the Summit53 plugin (recommended)

codex plugin marketplace add Summit53/skills
codex plugin add summit53@summit53

You can also open /plugins in Codex, choose the Summit53 marketplace and install from there. Codex asks you to sign in when the plugin installs.

Connector only

codex mcp add summit53 --url https://api.summit53.io/mcp

Codex opens a browser for Summit53 sign-in. Run codex mcp login summit53 to sign in again later.

Option 4: Connect to ChatGPT

If your ChatGPT plan and workspace support custom MCP apps, add Summit53 through Apps settings. The connection uses Summit53 OAuth for interactive authentication.

Steps

1. Open chatgpt.com and click on your profile icon, then Settings.
2. Navigate to Apps in the settings sidebar.
3. Click "Add app" or "Connect" and add a custom app using the MCP server URL:
   • URL: https://api.summit53.io/mcp
4. Authorize Summit53 via OAuth when prompted. Sign in with your Summit53 account credentials.
5. Once connected, Summit53 will appear in your Apps list. The actions shown are the functions available to that session’s scopes and Summit53 permissions.

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 5: Other MCP Clients (Cursor, Windsurf, VS Code)

Clients that support remote MCP servers connect to the endpoint directly: add a remote (Streamable HTTP) server with the URL https://api.summit53.io/mcp and sign in when the browser opens. For Cursor, add it in Settings → MCP or in .cursor/mcp.json:

{
  "mcpServers": {
    "summit53": {
      "url": "https://api.summit53.io/mcp"
    }
  }
}

If a client only supports local (stdio) servers, use the mcp-remote bridge as the server command instead. It handles the browser sign-in:

npx mcp-remote https://api.summit53.io/mcp

Token Management

After connecting a client, you can manage active tokens from the Summit53 MCP admin page at /admin/integrations/mcp.

Token Scopes

Connections made with the steps above register the client automatically. These standard connections are limited to read scopes plus job management: crm:read, pipeline:read, revenue:read, actions:read, coaching:read, meeting:read, jobs:read and jobs:manage. Write scopes are only available to trusted connections, and every write still needs a human approval.

Revoking Access

To cut off a client, click "Revoke All" next to the client name in the Connected Clients list. This immediately expires that client’s active access tokens for your organisation. To stop using a client for good, also remove the Summit53 connector or server entry from the client itself.

Scopes, Permissions, and Approval

Write functions always require their explicit write scope. Job Lifecycle functions always enforce jobs:read or jobs:manage, and Meetings functions always enforce meeting:read. Enforcement of the other read scopes is being rolled out behind a server setting. Summit53 organisation, ownership and role permissions apply to every request.

A scope authorises an operation; it does not prove that a human approved it. That is what action approvals are for.

Action Approvals

When action approvals are switched on, a small set of write actions can be run from an AI assistant, but only after you approve each one on a Summit53 review page. Nothing in Summit53 changes until the assistant submits the approved action.

Who can use approvals

• The assistant must connect through a trusted connection that the Summit53 team has set up for that client. Standard connections made with the steps above never see write actions.
• The trusted connection and your OAuth grant must both include the action’s write scope.
• You must be an approved member of the organisation.

Actions that can be approved: add an opportunity note, create or update a draft outreach sequence (sequences cannot be published this way), update an outreach lead, create, update or convert a target account, save, accept or dismiss researched stakeholder suggestions, start or update a Revenue Loop intervention, complete a coaching session, and record a coaching outcome. Publishing or enrolling sequences, sending outreach and Value Impact changes are not available to external assistants. See the MCP Tool Reference for the full list.

Approving a single action

1. Ask your assistant for the change. It prepares the action and gives you a review link. At this point no business change has been made.
2. Open the link. If you are not signed in, Summit53 asks you to sign in first (“Sign in to continue reviewing the requested Summit53 action.”). Only the person who requested the action can open it.
3. Under Human approval checkpoint, review the Exact material change: each field shows its Current and Proposed value, with a risk badge and the Server-enforced limits. The Review receipt panel shows the requesting client, the required scope, the expiry time and the argument fingerprint.
4. Select Approve exact action or Deny action. After approving, you can still select Cancel approval until the assistant uses it.
5. Return to the assistant. It submits the exact same action once, and the page shows Action executed.

Approval requests expire after 10 minutes by default. Approving does not extend that window. If the record changed after you reviewed it, or anything about the request differs, the action is refused rather than applied.

Approving a batch of outreach lead updates

Where batch approvals are also switched on, an assistant can stage up to 25 outreach lead updates for one review page, titled Review N outreach lead updates.

1. Each lead shows a table of Field, Current and Proposed values. Tick the updates you want; use Select all or Clear to speed this up. Anything left unticked is rejected.
2. Select Approve all N (or Approve X, reject Y), or Reject entire batch. Until the assistant runs the batch you can still select Cancel before execution.
3. The assistant then submits the batch. The page refreshes itself and shows each item as Applied, Rejected, Conflict — not applied or Failed — rolled back.

By default you have 30 minutes to review a batch, and the assistant has 30 minutes after your decision to run it. If a lead changed after you reviewed it, that item is skipped rather than overwritten.

Long-Running Work and Jobs

Long-running functions return a durable job response instead of holding the connection open. Use get_job to inspect status and results, list_jobs to find recent work, and cancel_job to request cancellation while a job is still cancellable. Job records are retained for 30 days.

Rate Limits

The MCP server enforces rate limits to ensure fair usage across your organization:

Some tools have lower limits due to computational cost or external API usage:

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 is an approved member of an active Summit53 organisation. If you use the mcp-remote bridge, check that Node.js v18+ is installed and npx is available in your PATH.

Tools not appearing after connection

Tools load when a conversation starts, so start a new conversation (or a new task in Codex) after connecting. In Claude Code, check that /mcp lists summit53 as connected. For ChatGPT, click "Refresh" in the connector information panel.

The assistant cannot make changes

Standard connections can’t change CRM records. Besides reading, they can only cancel their own background jobs, queue account research and generate your weekly action plan, and Claude asks before each of these. Write actions need a trusted connection, action approvals switched on and the matching write scope. Contact Summit53 support if your team needs this.

“Approval request unavailable”

The link is wrong, belongs to another user or organisation, or the request no longer exists. If the page says Approval expired, ask the assistant to prepare the action again.

Two Summit53 connectors are listed

Installing the Summit53 plugin alongside a connector you added manually gives two entries for the same organisation. That is harmless; remove the manual one if you prefer a single entry.

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

OAuth access tokens last one hour and rotating refresh tokens last seven days. Compatible clients refresh access automatically. If refresh is no longer possible, reconnect the client to complete a new authorization flow.

Next Steps

• MCP User Guide — Learn how to use Summit53 tools in your daily workflow
• MCP Tool Reference — Every function, prompt, resource and app the server publishes
• Integrations Overview — Connect Salesforce, Google Workspace, and other data sources
• Apply to the Founding 50 — Help shape the Revenue Engine in production