LEleapsurgebi
MCP Server

LeapSurge MCP — STAGING Entra (login check only)

Changed on

LeapSurge / Alkem Sales MCP Endpoint — STAGING Entra

Identical tools to /LeapSurgeR, but users sign in with the STAGING Entra app (dummy/test users). Use it to confirm the login flow works. These users have no scope rows in Databricks, so tools return "no data found" — that is expected here; the real numbers are validated on /LeapSurgeR.

The two endpoints are keyed by their token's environment (audience + issuer + tenant claim), so a staging token cannot be used on /LeapSurgeR and vice versa. require_mcp_auth derives the environment from this URL.

post/api/mcp/LeapSurgeRStg

Request

Headers

Mcp-Session-Idstring nullable

Request body

jsonrpcstring

JSON-RPC version. Always '2.0'

methodstring

MCP method: initialize | tools/list | tools/call

paramsobject nullable

Method parameters. For tools/call: { name, arguments }

idinteger nullable

Request ID. Echoed back in response.

Response

Successful Response

unknown required

Changes