## Problem `docs/source/local/access/mcp.md` is structured around `orbit mcp serve` and `glab orbit local mcp serve`. Neither command exists in orbit v0.58.0: ```shell $ orbit mcp serve error: unrecognized subcommand 'mcp' ``` The page currently shows `claude mcp add` and opencode configuration examples that would silently fail — users would add the MCP server config, see no connection errors, and then be confused why their AI agent can't query anything. This is the single most misleading page in the current docs tree. ## Proposed solution Rewrite `docs/source/local/access/mcp.md` as a **roadmap page** with a clear "Not yet available" callout at the top: ```markdown > **Note:** Local MCP (`orbit mcp serve`) is not yet available in orbit v0.58.0. > This page describes the planned interface. Track progress in issue #XXX. ``` Then preserve the documented planned interface (the `claude mcp add` examples, the opencode config block, the query shape) under a "Planned interface" heading — so the page remains useful as a spec for the contributor who will implement it, and for users who want to understand what's coming. **Do not** remove the page content — it's valuable as a spec. Just make the status unmistakably clear so users don't waste time trying to run it. Optionally: add a "Workaround" section showing how to use `glab orbit local query` from a terminal as a temporary substitute for agent access. ## Affected files - `docs/source/local/access/mcp.md` ## Validation - Page opens with a visible "Not yet available" callout - No `claude mcp add` examples appear as if they work today - `mise run lint:docs` passes - A new user reading the page understands immediately that this feature is not yet shipped ## Hackathon notes - **Difficulty:** L0 - **Estimated effort:** 1h - **No server needed:** Yes - **Prerequisites:** None — Markdown edit only - **How to test:** Show the page to someone unfamiliar with the project; they should immediately understand the feature is planned, not shipped