MCP Server
LeapSurge MCP — Claude & ChatGPT Connector
Changed onLeapSurge / Alkem Sales MCP Endpoint (Claude & ChatGPT Connector)
Curated primary-sales analytics over `datamarts.sandbox`. The endpoint
exposes one flexible analytics tool plus entity resolution, guarded SQL,
schema inspection and KPI-definition tools.
**URL:** `POST /api/mcp/LeapSurgeMCP`
**Header:**
- `Mcp-Session-Id` (optional but recommended) — echoed in every response.
**Methods Supported (`method`):**
- `initialize` — advertises `LEAPSURGE_SYSTEM_PROMPT` as MCP instructions
- `notifications/initialized`
- `ping`
- `tools/list`
- `tools/call`
**Example — List tools:**
{"jsonrpc":"2.0","method":"tools/list","params":{},"id":1}
**Example — Sales by division for FY2026:**
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "Sales",
"arguments": {
"measures": ["net_sales", "sale_qty"],
"group_by": ["division"],
"period": {"type": "fy", "value": "FY2026"},
"top_n": 10
}
},
"id": 1
}
**Tools**
- `Sales`
- `ResolveEntity`
- `RunSQL`
- `DescribeTable`
- `GetKpiDefinition`
**Security**
- Curated `Sales` SQL builder for normal analytics
- `RunSQL` is read-only, single-statement, table-allowlisted and row-limited
- Same Databricks connection as `/api/mcp/databricks`
- Session ID echoed to prevent connector session expiry
- ⚠️ NO authentication on this route and NO per-user row-level security —
every caller sees the full company dataset. Use `/api/mcp/LeapSurgeR` for
the OAuth-guarded, per-user row-level-secured variant.
post/api/mcp/LeapSurgeMCP
Request
- Base URLhttps://api.leapsurgebi.com (the document declares no server; this is the origin it was published from)
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Headers
Mcp-Session-Idstring nullable
Request body
Response
Successful Response
unknown required
Changes
- info
endpoint added
- info