---
title: "LeapSurge MCP — STAGING Entra (login check only)"
method: POST
path: "/api/mcp/LeapSurgeRStg"
tags: ["MCP Server"]
---

# LeapSurge MCP — STAGING Entra (login check only)

`POST /api/mcp/LeapSurgeRStg`

## 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/LeapSurgeRStg`
- Auth: none declared
- TypeScript: <https://skmtc.dev/leapsurgebi/apis/leapsurgeapi/docs/api/mcp/LeapSurgeRStg/post.ts> (a function with typed inputs; its response is checked against the schema)

**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.

## 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/LeapSurgeRStg/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)