Azure DevOps MCP Server
Brings on-premises Azure DevOps Server (including TFVC) to AI assistants with 49 tools for work items, repositories, pipelines, test plans, and wiki, along with profile-based secrets and write safety layers.
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
burcusipahioglu
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
AZURE_DEVOPS_AUDIT_LOGAZURE_DEVOPS_AUDIT_REDACTAudit privacy: add =1 to keep numeric IDs and field shape but drop all string values (titles, comments, branch names). Useful when work-item content carries classified data.AZURE_DEVOPS_ENABLED_DOMAINSwork_items,tfvc,pipelinesAZURE_DEVOPS_ENV_FILE/abs/path That exact pathAZURE_DEVOPS_MODEReadonly mode Server refuses all 8 write tools with a clear error; reads unaffected. CI, demos, sandbox, emergency stop =readonlyAZURE_DEVOPS_ORG_URLRestart the client. All 48 tools appear in the tool picker. Server name is auto-detected from (e.g. https://dev.azure.com/acme → acme); override with AZURE_DEVOPS_SERVER_NAME.AZURE_DEVOPS_PATmcp.json configs sync to the cloud (Claude Desktop, VS Code Settings Sync), get pasted into tickets, end up in dotfile repos. Inlining there is one git add . away from a public leak.AZURE_DEVOPS_PROFILEProfile-based secrets =name → gitignored .env.<name>; no PAT in cloud-synced mcp.json. Multi-instance is a natural byproduct.AZURE_DEVOPS_PROJECTYourProjectNameAZURE_DEVOPS_RATE_LIMIT_WRITES_PER_MINRate limit Global sliding 60s window across all writes — runaway-loop fence, not a throughput regulator =10 (default; 0 disables)AZURE_DEVOPS_RESOURCE_DIRAZURE_DEVOPS_SERVER_NAMERestart the client. All 48 tools appear in the tool picker. Server name is auto-detected from AZURE_DEVOPS_ORG_URL (e.g. https://dev.azure.com/acme → acme); override with .AZURE_DEVOPS_SSL_IGNORE=true # uncomment for self-signed certsTool inputs are validated
45/48 tool handlers declare input schemas (94%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
Only 4/48 tool handlers wrap calls in try/catch (8%)
Wrap each tool handler body in try/catch and return a structured error response.
Tests exist
No test files found
Add tests that exercise each declared tool.
Domain consistency
npm scope @burcusg doesn't match GitHub owner burcusipahioglu
Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/burcusipahioglu/azure-devops-mcp-onprem)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check