Summit53 MCP Server

Bring Summit53's Revenue Engine into the AI workflows your team already uses.

This package connects MCP-compatible assistants to Summit53's hosted Revenue Engine. Assistants can help diagnose pipeline and forecast gaps, decide the next best action, execute permitted workflows, and preserve value evidence around the Figure-Eight revenue loop — from acquisition through expansion and back into acquisition.

Quick start

Add the package to a stdio-based MCP client such as Claude Desktop, Claude Code, Cursor, Windsurf, or Codex:

{
  "mcpServers": {
    "summit53": {
      "command": "npx",
      "args": ["-y", "@summit53/mcp-server"]
    }
  }
}

On first use, your browser opens the Summit53 OAuth flow. Sign in, review the requested access, and authorize the client. Tokens are cached by the local MCP bridge and refreshed automatically.

For a web client that supports custom remote MCP connections, add:

• Name: Summit53
• URL: https://api.summit53.io/mcp

Client availability and labels vary by plan and workspace. Use the custom server URL instead of relying on a public app-directory listing.

See the MCP setup guide for client-specific instructions.

What the Revenue Engine enables

Ask in natural language to:

• diagnose pipeline risk, deal drag, forecast confidence, gaps, and capacity;
• prepare opportunity strategy, account reviews, weekly action plans, and coaching;
• research accounts and inspect notes, activity, outreach, value impact, and methodology knowledge;
• write permitted notes, outreach updates, value evidence, and coaching outcomes;
• track long-running work through a durable job lifecycle.

The current release gate freezes 75 externally published functions across 15 categories. That count is a compatibility fact, not the product proposition. Tool visibility depends on the client's granted scopes and the user's Summit53 organization permissions; call list_available_tools to discover the surface available in the current session.

The exact machine-readable surface is maintained in tool-catalog.json. The registry-compatible connection manifest is server.json. The tool reference explains inputs, outputs, access requirements, and async behavior.

Authentication and permissions

Interactive connections use OAuth 2.1-style authorization with PKCE. Access tokens last one hour; rotating refresh tokens last seven days. Access can be revoked from /admin/integrations/mcp in Summit53.

The published scope set is:

• read: crm:read, pipeline:read, revenue:read, actions:read, jobs:read;
• write and operations: crm:write, outreach:write, outreach:send, coaching:write, value:write, automation:manage, jobs:manage.

Business write tools always require their explicit write scopes. Job lifecycle tools always enforce jobs:read or jobs:manage. Read-scope enforcement for the remaining catalogue is being rolled out behind a production gate. Summit53's organization, ownership, and role permissions remain

... View full README on GitHub