mcp

Mcp Workspace Get

GET on the workspace endpoint: 405, for the reason :func:mcp_get gives.

Same answer as the per-repo surface and deliberately not a friendlier one: a 200 on a GET reads to a Streamable HTTP client as a stream that died on connect, and it reconnects forever. That cost us 80% of production request volume for a month in July 2026.

Shadowing note: this route also swallows GET /mcp/w/<repo> for the owner "w", as the POST one does. Harmless, both are the same 405, but the hint text should still name the URL the caller actually used.

get/mcp/w/{workspace_id}

Path parameters

workspace_idstring required

Response

Successful Response

{"stackTrail":"paths:/mcp/w/{workspace_id}:get:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes