install-azure-devops-mcp
Skill2 starsChanged 13 days agoMITView on GitHub
Install and configure the Azure DevOps MCP server for Claude or GitHub Copilot agents. Use when setting up Azure DevOps MCP, ADO MCP, work items, repos, pipelines, sprints, wikis, or asked to install azure devops mcp.
- Reads credentials
- Installs packages
In this repository18 other files it gives its agents.
- ado-open-prSkill
- ado-pr-code-reviewSkill
- ado-pr-resolve-commentsSkill
- ado-pr-teams-notifySkill
- agent-playtestSkill
- explain-diff-htmlSkill
- generate-pr-notesSkill
- git-commit-conventional-strictSkill
- install-atlassian-mcpSkill
- install-playwright-mcpSkill
- install-sentry-mcpSkill
- prd-to-sdd-specSkill
- sdd-qa-to-ticketSkill
- setup-project-configSkill
- spec-recalibrateSkill
- sync-api-specSkill
- tech-plan-to-ticketSkill
- tech-plan-to-wikiSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
All optional — anything not passed is asked in Step 1.
- Very specific: line 59
If ~/.env.mcp-azure-devops already exists, the script detects it and asks whether to reuse the stored PAT — no re-entry needed
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Install Azure DevOps MCP
Install this skill
npx skills add jamesyang124/agent-skills --skill install-azure-devops-mcp -gAdds Azure DevOps access to your agent: work items, repos, branches, PRs, pipelines, test plans, sprints, wikis. Repository: https://github.com/microsoft/azure-devops-mcp
Arguments
All optional — anything not passed is asked in Step 1.
| Token | Meaning |
claude / copilot | which agent to configure |
| any other bare token | Azure DevOps organization name (e.g. mycompany) |
The PAT is never taken as an argument — it is collected in the terminal (Step 2).
Quick Start
Collect parameters, then run the bundled script. The PAT must be collected via terminal — never via a questions tool.
Step 1 — Collect parameters
Use vscode_askQuestions with:
- agent — which agent to configure
- options:
claude,copilot
- options:
- org — Azure DevOps organization name (e.g.
mycompany)
Step 2 — Run the installer
Find this skill's directory from the SKILL.md path, then run:
PROJECT_ROOT="<workspace-root>" \
bash "<skill-dir>/scripts/install.sh" \
--agent <agent> \
--org <org><skill-dir> is this skill's folder, the base directory shown when the skill loads (for example ~/.claude/skills/install-azure-devops-mcp).
- Set
PROJECT_ROOTto the user's current workspace folder - If
~/.env.mcp-azure-devopsalready exists, the script detects it and asks whether to reuse the stored PAT — no re-entry needed - PAT is always prompted interactively in the terminal (hidden input) when no existing file is found
- The script merges into any existing config file; it will not overwrite other servers
PAT scopes required:
- Work Items (Read & Write)
- Code (Read)
- Build (Read)
- Test (Read)
Create at: https://dev.azure.com/<org>/_usersSettings/tokens
Step 3 — Confirm
Tell the user: Restart your agent to load Azure DevOps MCP.
What Gets Written
Copilot (.vscode/mcp.json):
{
"servers": {
"azure-devops-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@azure-devops/mcp", "<org>"],
"env": { "AZURE_DEVOPS_EXT_PAT": "<pat>" }
}
}
}Claude (.mcp.json):
{
"mcpServers": {
"azure-devops-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@azure-devops/mcp", "<org>"],
"env": { "AZURE_DEVOPS_EXT_PAT": "<pat>" }
}
}
}An env file is also written to ~/.env.mcp-azure-devops (global, chmod 600).
Troubleshooting
npx not found→ install Node.js from https://nodejs.org/jq not found→brew install jqon macOS- Authentication errors → verify PAT scopes and expiry
- Config not loading → confirm the agent was fully restarted after install
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

