---
title: "Mcp Workspace Get"
method: GET
path: "/mcp/w/{workspace_id}"
tags: ["mcp"]
---

# Mcp Workspace Get

`GET /mcp/w/{workspace_id}`

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.

## Path parameters

- `workspace_id` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

## Changes

- **2026-09-18** `d1694e41a8a1` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/repowise/apis/repowise-hosted-api/changes/mcp/w/:workspace_id/get.md)

---

[API](https://skmtc.dev/repowise/apis/repowise-hosted-api.md) · [All operations](https://skmtc.dev/repowise/apis/repowise-hosted-api/llms.txt) · [OpenAPI document](https://skmtc.dev/repowise/apis/repowise-hosted-api/revisions/cce15d886f2b?raw)