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

# Mcp Workspace Endpoint

`POST /mcp/w/{workspace_id}`

JSON-RPC entry point for an MCP client targeting a whole workspace.

One endpoint, one existing user-scoped API key, N indexed repos. Tools are
the same ones the per-repo endpoint serves; they are run against every
ready member snapshot and merged by the dispatcher workspace chat already
uses, so the two surfaces cannot drift in what "across the workspace"
means.

No per-repo tool override is read here. ``mcp_tool_overrides`` is keyed
``(user_id, repo_id)`` and a workspace has several repos, so honouring
five possibly-contradictory selections would be a guess; the workspace
surface is the curated default plus ``list_repos``. Upgrade path if
anyone asks: a workspace-keyed override row, not a merge of repo rows.

## 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/post.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/98c833b3480d?raw)