Azure DevOps MCPWhat is this?
This is a self-hosted gateway that puts Azure DevOps in front of your AI tools. Microsoft ships an official Azure DevOps MCP server, but it's built for one person on one machine: a single token, a single organization, talking over a local pipe. This service wraps that server and exposes it as a proper authenticated endpoint on the internet that many people can share — each with their own private set of Azure DevOps connections.
What it does
- • Gives every account its own isolated Azure DevOps connections — your token is never reachable by anyone else.
- • Speaks the Model Context Protocol (MCP), so MCP-aware clients like Claude can call Azure DevOps tools (work items, repos, pipelines, and more).
- • Stores your Azure DevOps personal access token encrypted at rest and decrypts it only to talk to Azure DevOps on your behalf.
- • Keeps an audit log of the calls made through your account, and tracks the upstream Microsoft server, upgrading it automatically in the background.
Getting started
- 1. Create an account. Registration is open — sign up with a passkey (Touch ID, Windows Hello, a security key, or your phone). No password to remember or leak.
- 2. Add a connection. Under Connections, give it your Azure DevOps organization and a personal access token (PAT). Use the narrowest scopes and shortest expiry you can — see the tips below.
- 3. Connect your MCP client. Two ways:
- • OAuth — clients that support remote MCP (e.g. Claude) just point at the endpoint and you authorize with your passkey.
- • API token — create one under Tokens and send it as Authorization: Bearer <token>.
- 4. Discover tools. Tools are namespaced <slug>__<tool> per connection. Call list_connections from your client to see what's available.
About your credentials
Your PAT is encrypted at rest and scoped to your account alone. Still, this is a personal, best-effort project, not a professionally operated service — so provision your PAT with the narrowest scopes and shortest expiry you can live with, and revoke it in Azure DevOps the moment you stop using it. Full details are in the privacy & disclaimer.
Run your own
Don't want to trust someone else's server with your Azure DevOps token? Fair. The whole thing is open source and ships as a single self-hosted container — clone it and run your own instance: