Azure DevOps MCP Tool Reference

OpenAPI-style static reference docs for the remote Azure DevOps MCP server — every tool, its parameters and annotations, and correct tools/call examples across all toolsets.

🔗 Live site: https://waynegoosen.com/azure-devops-mcp-docs/

What this is

A single static site, generated from the MCP server's own capability manifest, that lets you browse:

• All tools grouped by toolset (repositories, work items, pipelines, wiki, search, and more)
• Each tool's input schema, parameters, and annotations
• Copy-pasteable tools/call request examples
• A guide for configuring your MCP client

The site is built by src/render.ts from the JSON capability data in data/. It is plain HTML/CSS with no client-side framework and no build-time network access, so it deploys anywhere static.

Local development

Requires Node.js 20+.

npm install        # install dependencies
npm run build      # render data/ → public/
npm run preview    # serve public/ locally

npm run build reads the committed data in data/ and writes the site to public/. Set SITE_URL to emit absolute canonical/OG URLs plus robots.txt and sitemap.xml (CI sets this automatically to the Pages URL):

SITE_URL=https://waynegoosen.com/azure-devops-mcp-docs npm run build

Refreshing the tool data

data/*.json is scraped from the Azure DevOps MCP server. The default local mode spawns the official @azure-devops/mcp package over stdio and needs no credentials (tool definitions are static in the server):

ADO_ORG=your-org npm run scrape   # refresh data/
npm run build                     # re-render
# or both at once:
ADO_ORG=your-org npm run build:full

See the header of src/scrape.ts for remote-mode options against a hosted endpoint.

Deployment

Deployment is fully automated. On every push to main, the Deploy workflow builds the site with the correct SITE_URL and publishes it to GitHub Pages. The CI workflow type-checks and builds on every pull request.

One-time setup: In the repository, go to Settings → Pages → Build and deployment → Source and select GitHub Actions.

Project layout

Path	Purpose
src/render.ts	Generates the static site from data/ into public/
src/scrape.ts	Scrapes tool definitions from the MCP server into data/
src/toolsets.ts, src/examples.ts	Toolset grouping and example request data
data/	Committed capability data the site is built from
fixtures/	Small sample data used for local testing
public/	Build output (generated, git-ignored)

Contributing

Contributions are welcome — see CONTRIBUTING.md.

License

MIT © Wayne Goosen