Summit53 Revenue Engine — Claude Code MCP server: setup and usage
Connects coding assistants to Summit53's revenue engine for pipeline diagnosis and forecasting. It surfaces deal risks and tracks team follow-ups directly in chat.
claude mcp add --transport http mcp-server https://api.summit53.io/mcpWhat Summit53 Revenue Engine does
This integration exposes Summit53 pipeline analytics to AI assistants via HTTP at https://api.summit53.io/mcp or through a local stdio runner with npx. The engine groups tools across areas such as forecasting, deal strategy, CRM notes, and risk auditing. Session access filters down according to assigned workspace permissions.
Tasks that take time to compute run as background jobs instead of blocking open requests. You can check progress with get_job, list past runs, and view retained job data for up to 30 days. Logins rely on OAuth 2.1 with PKCE; access tokens expire after one hour while refresh tokens stay valid for seven days.
Every write action strictly requires dedicated permissions like crm:write or outreach:send. Without a configured Summit53 organization account, the assistant cannot pull pipeline metrics or alter records.
What it helps with
- identify stalled deals and pipeline risks
- build weekly account action plans
- inspect background job progress using
get_job - record approved coaching notes and outreach entries
Example prompts for the agent
- Review current pipeline risks and highlight deals that stalled.
- Check the status of background task
job_123withget_job. - Draft a strategic plan for next week's account renewals.
How to install Summit53 Revenue Engine
1Platform CLI: remote server
claude mcp add --transport http mcp-server https://api.summit53.io/mcp2Platform CLI
claude mcp add summit53-revenue-engine -- npx -y @summit53/mcp-server1Platform CLI: remote server
codex mcp add summit53-revenue-engine --url https://api.summit53.io/mcp2Platform CLI
codex mcp add summit53-revenue-engine -- npx -y @summit53/mcp-serverConfig file
{
"mcpServers": {
"summit53-revenue-engine": {
"url": "https://api.summit53.io/mcp"
}
}
}{
"mcpServers": {
"summit53-revenue-engine": {
"command": "npx",
"args": [
"-y",
"@summit53/mcp-server"
]
}
}
}Config file
{
"servers": {
"summit53-revenue-engine": {
"type": "http",
"url": "https://api.summit53.io/mcp"
}
}
}{
"servers": {
"summit53-revenue-engine": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@summit53/mcp-server"
]
}
}
}1Platform CLI: remote server
gemini mcp add -t http summit53-revenue-engine https://api.summit53.io/mcp2Platform CLI
gemini mcp add summit53-revenue-engine npx -y @summit53/mcp-serverStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Summit53 Revenue Engine
How to install Summit53 Revenue Engine in Claude Code?
Run claude mcp add --transport http summit53-revenue-engine https://api.summit53.io/mcp in your terminal. Complete the browser login flow when prompted.
What does Summit53 Revenue Engine do?
It lets assistants evaluate sales pipeline risks, review forecast confidence, and manage revenue actions against Summit53 data.
How does authentication work for this server?
Connections authenticate via OAuth 2.1 with PKCE in your web browser. The server caches tokens locally and refreshes them automatically.
