MCP server for on-premises Azure DevOps Server (TFS) with TFVC support - shelvesets, changesets, Work Items, Git, Pipelines, Wiki for AI assistants.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"azure-devops": {
"env": {
"AZURE_DEVOPS_ENV_FILE": "C:\\Users\\you\\.azure-devops-mcp.env"
},
"args": [
"-y",
"@burcusg/azure-devops-mcp-onprem"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for on-premises Azure DevOps Server (TFS). Covers Work Items, Git, TFVC (including shelvesets, changesets, labels), Pipelines, Wiki, and Test Plans. Profile-based multi-tenant config, PAT authentication. Bridges Claude, GitHub Copilot, Cursor, Antigravity, and other AI assistants.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@burcusg/azure-devops-mcp-onprem' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @burcusg/azure-devops-mcp-onprem against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / cloud / education
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Persistent memory using a knowledge graph
An autonomous agent that conducts deep research on any data using any LLM providers
MCP Security Weekly
Get CVE alerts and security updates for Azure Devops Mcp Onprem and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Governed access to on-prem Azure DevOps (including TFVC) for AI agents and assistants, with typed tools, chainable workflows, and a server-side write-safety layer.
Query work items, repositories, and pipelines in natural language — running locally, no cloud proxy, no telemetry.
Coverage · TFVC · Profiles · Write Safety · Setup
| TFVC native | 10 dedicated tools — shelvesets (incl. shelved file content), changesets, diffs, work-item linkage. The reason this server exists. |
| Write safety | 6 layers — MCP annotations · confirmation directive · readonly kill switch · rate limit · dry-run on every write · audit log |
| Local / on-prem only | PAT auth, no cloud proxy, no third-party calls, no telemetry |
| 48 tools / 6 domains | Work Items · Git · TFVC · Pipelines · Wiki · Test Plans |
| Typed results | outputSchema + structuredContent on the 8 most-chained read tools — schema-validated results an agent can chain into the next tool without parsing prose |
@me token | owner / author / reviewer / assignedTo accept @me — resolved per tenant, stateless for multi-agent setups |
| PR review flow | /review_pull_request → structured advisory review → on request, published to the PR as file-anchored comments, each one confirmed first |
| Profile-based secrets | AZURE_DEVOPS_PROFILE=name → gitignored .env.<name>; no PAT in cloud-synced mcp.json. Multi-instance is a natural byproduct. |
| AI clients | Claude (Code/Desktop), GitHub Copilot, Cursor, Visual Studio Code — any MCP-compatible client |
"Show me all active bugs assigned to me in this sprint" "What changed in changeset 12345?" "Review PR 123 and post the findings as comments" "List my latest shelvesets" "Trigger the nightly build on the release branch"
One server across the whole development cycle — Plan, Code, Review, Build & Release, Test, Document — with your own templates exposed as MCP resources alongside the built-in tools and prompts. Every write passes a server-side governance layer — readonly mode, dry-run preview, rate limit, and audit log (see Write Safety); tools can also be scoped per role (see Restrict tools per role below).
Full per-tool parameter reference: Tool Reference ↓