MCP Documentation Server¶

@whizbang/docs-mcp-server is a Model Context Protocol server that gives AI assistants (Claude Code, Claude Desktop, Cursor, or any MCP client) direct, structured access to this documentation — search, code examples, code↔docs↔tests navigation, and live CI test status.

Quick start¶

No install required — point your MCP client at npx with @latest so it always pulls the current published build:

{
  "mcpServers": {
    "whizbang-docs": {
      "command": "npx",
      "args": ["-y", "@whizbang/docs-mcp-server@latest"]
    }
  }
}

Or register it with the Claude Code CLI:

claude mcp add whizbang-docs -- npx -y @whizbang/docs-mcp-server@latest

Prefer a global install (e.g. for Cursor or a shared machine)? The whizbang-docs-mcp binary is on your PATH afterward:

npm install -g @whizbang/docs-mcp-server@latest

The npm package bundles a versioned snapshot of these docs (works offline; bundle-info.json records the source commit). Live test status is always fetched from the site so it can never go stale.

:::note Versioning: the package version tracks the Whizbang library release it documents (e.g. 0.860.8-alpha.9). Whizbang is pre-1.0, so the published versions are prereleases — @latest resolves to the newest one. Pin a specific build with @whizbang/docs-mcp-server@0.860.8-alpha.9 if you need reproducibility. :::

What your assistant can do with it¶

Tool	Purpose
`search-docs`	Full-text/semantic search across all pages
`find-examples`	Find C# examples by topic, framework, difficulty
`list-categories` / `list-docs-by-category`	Browse the docs structure
`get-code-location`	Where in the library a documented concept is implemented
`get-related-docs`	Which pages document a given code symbol
`get-tests-for-code` / `get-code-for-test`	Navigate the code↔tests map (thousands of linked test methods)
`get-test-status`	Live pass/fail for a test class or method from the latest library CI run
`validate-doc-links` / `validate-test-links`	Integrity checks over the linking system
`get-coverage-stats`	How much of the public API has linked tests

Example: ask "is the dispatcher's delivery-receipt behavior actually passing on develop?" — the assistant calls get-tests-for-code on Dispatcher, then get-test-status on DispatcherTests, and answers from real CI data.

Contributor mode¶

Running from a checkout of the docs repo uses the live files automatically (no bundled snapshot). Point it elsewhere explicitly with:

DOCS_PATH=/path/to/whizbang-lib.github.io/src/assets/docs npx @whizbang/docs-mcp-server

See the contributor documentation for the full development workflow, and mcp-docs-server/README.md in the repo for all environment variables.