← ClaudeAtlas

azure-devopslisted

Use when user references Azure DevOps / ADO, dev.azure.com or an on-prem TFS URL, work items, bugs, PBIs, pull requests, or the project wiki. Goes through the azure-devops MCP server.
tuannv14/claude-team-toolkit · ★ 1 · DevOps & Infrastructure · score 68
Install: claude install-skill tuannv14/claude-team-toolkit
# /azure-devops — Azure DevOps through MCP Everything goes through the **`azure-devops` MCP server**. This skill issues no REST calls to `/_apis/` and has no curl fallback. Wiring, the on-premises caveats and permission tiers: [docs/mcp-servers.md](../../docs/mcp-servers.md). ## First, check the server is there Tools appear as `mcp__azure-devops__<tool>`. If none are available, say so and stop — do not build a `/_apis/` URL and curl it, which is what the MCP-only guard hook refuses. Check with `claude mcp list`. `whoami` is the cheapest way to confirm the server is up and the PAT is live. ## When to Use - Work items: read one, search, or list by type (bugs, tasks, PBIs, features) - Pull requests: what is open, and what a PR changed - Repo and branch inventory - Reading the project wiki ## When NOT to Use - Cloning, committing, pushing → plain `git`, which is untouched by the guards - Editing wiki content → the web UI - Pipeline runs and build logs → no tool covers these; use the web UI - Azure DevOps **Services** with Microsoft's own server → the tool names below are from a vendored on-prem server and will not match ## Tool map All read: | You want | Tool | |---|---| | confirm auth | `whoami` | | projects, repos, branches | `list-projects`, `list-repos`, `list-branches` | | pull requests | `list-pull-requests` | | what a PR changed | `get-pr-changes` | | one work item | `get-workitem-detail` | | find work items | `search-workitems` | | work items by type | `list