Joshuaramirez Ms Ado Az Claude Code Plugin
joshuaramirez-ms-ado-az-claude-code-plugin is a Claude Code plugin for the Build phase that connects Azure DevOps work tracking to the agent via Azure CLI instead of the MS MCP server.
Install this plugin when you want Claude Code to manage Azure DevOps work items, boards, and sprints through the stable Azure CLI instead of the buggy Microsoft MCP server.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install joshuaramirez-ms-ado-az-claude-code-plugin@JoshuaRamirez/ms-ado-az-claude-code-pluginBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:JoshuaRamirez/ms-ado-az-claude-code-plugin") and the paste-ready config with skillselion.get_install_config("plugin:JoshuaRamirez/ms-ado-az-claude-code-plugin").
What it does
joshuaramirez-ms-ado-az-claude-code-plugin is a Claude Code integration for teams that live in Azure DevOps but want agent access through Azure CLI rather than the Microsoft MCP server called out as buggy in the listing description. Solo builders wearing the PM hat can use it to reason about work items, backlogs, boards, and sprints while coding—bridging the gap between IDE-side agent work and org-wide tracking in ADO. The catalog tags it under integrations with azure, devops, and work-item keywords, which signals task-focused DevOps tooling rather than a methodology skill. You should expect to authenticate and configure az for your tenant and projects before commands succeed; the plugin does not replace Azure portal governance or pipeline authoring by itself. It shines when you need fast, scriptable ADO reads and updates from Claude Code during feature work, sprint planning touch-ups, or incident follow-ups that spawn work items. Intermediate complexity is appropriate because Azure identity, project scoping, and CLI flags are on you. Treat outcomes as tighter loops between code changes and ADO state, not as a full replacement for Azure Boards UI workflows.
Highlights
- Azure DevOps integration for Claude Code using Azure CLI (az), explicitly avoiding the MS MCP server path
- Keywords cover ADO, azure-devops, work-items, backlogs, boards, sprints, and management
- Integrations-category listing aimed at builders already on Azure DevOps
- Single-plugin bundle (pluginCount: 1) from JoshuaRamirez/ms-ado-az-claude-code-plugin
- Fits querying and updating work tracking without leaving the agent session
Why builders use it
Claude Code users on Azure DevOps get blocked or frustrated when the official MCP path is unreliable, so work items and sprints fall out of sync with agent sessions.
After install and az login, you can drive boards, backlogs, sprints, and work-item management from Claude Code with a CLI-backed integration the listing positions as more dependable than the MS MCP server.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is joshuaramirez-ms-ado-az-claude-code-plugin for?
It is for Claude Code users who run Azure DevOps for backlogs, boards, and sprints and want agent-driven ADO actions through az rather than the MS MCP server.
When should I use joshuaramirez-ms-ado-az-claude-code-plugin?
Use it during Build (and Operate follow-ups) when you need to query or update work items, sprints, or boards from the agent while implementing features or triaging production work.
How do I add joshuaramirez-ms-ado-az-claude-code-plugin to my agent?
Add the JoshuaRamirez/ms-ado-az-claude-code-plugin bundle from the catalog in Claude Code, install Azure CLI, sign in with az login, and scope permissions for your DevOps organization and projects.
Comments
Share how you use joshuaramirez-ms-ado-az-claude-code-plugin, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.