---
title: "LeapSurge MCP — Claude & ChatGPT Connector"
method: POST
path: "/api/mcp/LeapSurgeMCP"
tags: ["MCP Server"]
---

# LeapSurge MCP — Claude & ChatGPT Connector

`POST /api/mcp/LeapSurgeMCP`

## Request

- Base URL: `https://api.leapsurgebi.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.leapsurgebi.com/api/mcp/LeapSurgeMCP`
- Auth: none declared
- TypeScript: <https://skmtc.dev/leapsurgebi/apis/leapsurgeapi/docs/api/mcp/LeapSurgeMCP/post.ts> (a function with typed inputs; its response is checked against the schema)

**LeapSurge / 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:**
```json
    {"jsonrpc":"2.0","method":"tools/list","params":{},"id":1}
```

    **Example — Sales by division for FY2026:**
```json
    {
      "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.

## Headers

- `Mcp-Session-Id` string, nullable

## Request body

- MCPRequest
  - `jsonrpc` string: JSON-RPC version. Always '2.0'
  - `method` string: MCP method: initialize | tools/list | tools/call
  - `params` object, nullable: Method parameters. For tools/call: { name, arguments }
  - `id` integer, nullable: Request ID. Echoed back in response.

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

## Changes

- **2026-09-24** `23b42df3193a`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/leapsurgebi/apis/leapsurgeapi/changes/api/mcp/LeapSurgeMCP/post.md)

---

[API](https://skmtc.dev/leapsurgebi/apis/leapsurgeapi.md) - [All operations](https://skmtc.dev/leapsurgebi/apis/leapsurgeapi/llms.txt) - [OpenAPI document](https://skmtc.dev/leapsurgebi/apis/leapsurgeapi/revisions/13653cb8ee76?raw)