MCP server for interacting with Azure DevOps (on-premises) WEM fork
MCP server for interacting with Azure DevOps (on-premises) WEM fork. That is what the ado mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This project provides a lightweight server to interact with on-premises Azure DevOps, enabling automation, project management, and streamlined workflows.
The server publishes 2 tools. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — In your project, add a .vscode\mcp.json file and setup environment varibales with the following content:Configuration is passed through the environment: LOG_LEVEL, ADO_MCP_MODE, ADO_MCP_AUTH_TYPE, ADO_MCP_ORG_URL, ADO_MCP_API_VERSION, ADO_MCP_BATCH_API_VERSION, ADO_MCP_MARKDOWN_COMMENTS_API_VERSION, NODE_EXTRA_CA_CERTS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as args, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ado's toolset — Prerequisites, Installation — is a fair guide to whether it matches your workflow. It is maintained by lotfihoc; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Ado's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | In your project, add a .vscode\mcp.json file and setup environment varibales with the following content: |
{
"mcpServers": {
"prem": {
"command": "npx",
"args": ["-y", "args"],
"env": {
"LOG_LEVEL": "your-value",
"ADO_MCP_MODE": "your-value",
"ADO_MCP_AUTH_TYPE": "your-value",
"ADO_MCP_ORG_URL": "your-value",
"ADO_MCP_API_VERSION": "your-value",
"ADO_MCP_BATCH_API_VERSION": "your-value",
"ADO_MCP_MARKDOWN_COMMENTS_API_VERSION": "your-value",
"NODE_EXTRA_CA_CERTS": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| LOG_LEVEL | Configuration value read at startup. | Optional |
| ADO_MCP_MODE | Configuration value read at startup. | Optional |
| ADO_MCP_AUTH_TYPE | Configuration value read at startup. | Optional |
| ADO_MCP_ORG_URL | Endpoint or connection string the server talks to. | Yes |
| ADO_MCP_API_VERSION | Configuration value read at startup. | Optional |
| ADO_MCP_BATCH_API_VERSION | Configuration value read at startup. | Optional |
| ADO_MCP_MARKDOWN_COMMENTS_API_VERSION | Configuration value read at startup. | Optional |
| NODE_EXTRA_CA_CERTS | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.