# Azure DevOps MCP > Azure DevOps MCP connects your agent directly into your CI/CD workflow. You can check project status, track work items, monitor build history, and manage repositories across any Azure DevOps organization without leaving your client. ## Overview - **Category:** industry-titans - **Price:** Free - **Tags:** ci-cd, pipeline-management, work-item-tracking, software-development, agile, bug-tracking ## Description You need visibility into the entire software development lifecycle—from story definition to deployment artifact. This MCP lets your AI client query everything in your Azure DevOps environment through natural conversation. You can list all projects in an organization or drill down into specific teams and repositories within a project. Need to know if a feature is blocked? Query work items to see status changes, track bugs, or check user stories. Want to know if the code deployed correctly? List pipelines and review recent build history right from your agent. If you're using Vinkius, this MCP gives you instant access to all those operational details, letting your agent act as a centralized dashboard for your entire DevOps setup. ## Tools ### list_builds Gets a list of recent build executions, showing their completion status and who triggered them. ### list_pipelines Retrieves the definitions and current status for all defined CI/CD pipelines in your project. ### list_projects Retrieves metadata for every active and archived project in the entire organization. ### list_repositories Shows all Git repositories linked to a project, helping you pinpoint code storage locations. ### list_project_teams Lists all team structures within a specific project to understand who owns which components. ### list_work_items Queries and lists recent work items, such as bugs or user stories, based on filters like status or assignee. ## Prompt Examples **Prompt:** ``` List all active projects in my Azure DevOps organization. ``` **Response:** ``` I've retrieved your projects. You have access to: 'Mobile App', 'Internal Tools', and 'Infrastructure-as-Code'. Which one would you like to see work items for? ``` **Prompt:** ``` Show me the last 5 work items for the 'Mobile App' project. ``` **Response:** ``` I've fetched the work items. There are 5 recent items including 'Bug #8823: Login crash', 'Story #8824: Add dark mode', and 'Task #8825: Update SDK'. Would you like more details on the login crash? ``` **Prompt:** ``` What is the status of the latest build for project 'Internal Tools'? ``` **Response:** ``` Retrieving build history... The latest build for 'Internal Tools' (ID: 10293) was 'Succeeded' 2 hours ago. It was triggered by Mike Ross on the 'main' branch. ``` ## Capabilities ### Project Visibility List and retrieve metadata for every project in an organization or list specific teams within a project. ### Work Item Management Query recent work items, allowing you to track bugs, stories, and tasks across your team’s backlog. ### Code & Repository Access List all available Git repositories within a project for code source tracking. ### Pipeline Monitoring View defined CI/CD pipelines and fetch the history, status, or metadata of recent build executions. ## Use Cases ### The Feature Freeze Check A Product Owner needs to know if three key features are ready for release. They ask their agent, which then uses `list_work_items` to check the status of all related stories and flags any that are stuck in 'Review' status. ### The Deployment Failure Investigation A DevOps Specialist gets an alert. They ask their agent, which immediately uses `list_builds` and `list_pipelines`. The agent provides the failure ID and suggests checking the repository via `list_repositories` for recent commits. ### The Team Restructure Audit A manager needs to know who is on which team after a merger. They ask their agent, running `list_project_teams`, getting an immediate breakdown of organizational assignments across the entire project set. ### Initial Project Assessment A new developer joins and needs to know what code base they should look at. They use `list_projects` first, then drill down with `list_repositories` on the correct project ID to find the starting point. ## Benefits - Cut down on manual checking. Instead of navigating to the pipeline dashboard, you ask your agent about `list_pipelines` status directly in your chat. - Stop hunting for code sources. You can use `list_repositories` to quickly see all linked Git repos without leaving your IDE or terminal. - Get a single view of project health. Use `list_projects` and then follow up with `list_work_items` to check the backlog status in one conversation flow. - Understand team structure instantly. Running `list_project_teams` gives you an overview of who is assigned to what, removing coordination guesswork. - Accelerate debugging. If a build fails, your agent can use `list_builds` to pull up the failure history and tell you exactly when it happened. ## How It Works The bottom line is you manage your DevOps ecosystem by talking to it, not by clicking through dashboards. 1. Subscribe to this MCP and provide your Azure DevOps Organization name and Personal Access Token (PAT). 2. Connect your preferred AI agent client. The connection authenticates your permissions across the organization. 3. Ask your agent a direct question, like 'What was the status of the last build for Project X?' Your agent executes the necessary tool call and reports the real-time data. ## Frequently Asked Questions **How do I use list_work_items in Azure DevOps?** You query this tool by specifying filters like status, assignee, or type (bug/story). This lets you pull a targeted list of items without having to manually filter the dashboard. **What is the difference between list_pipelines and list_builds?** The pipelines define the workflow steps. The builds track the actual, executed history of those workflows. You need `list_pipelines` to see *how* it runs, and `list_builds` to see if the last run succeeded. **Can I find all my code locations using list_repositories?** Yes. This tool queries every Git repository attached to a project, giving you an inventory of where the source code is stored within your organization's scope. **Does this MCP help with team coordination? (list_project_teams)** It lists all defined teams and their members for a given project. This helps you understand the operational structure without needing to contact anyone. **What authentication method does the MCP use when running list_projects?** It requires a Personal Access Token (PAT) paired with your Azure DevOps organization URL. This PAT must have read scope permissions for Project and Work Item services to ensure the tool can properly enumerate all available projects. **Can I filter my results when calling list_pipelines by environment?** Yes, you specify the desired environment name or ID as part of the query parameters. This allows your agent to narrow down pipeline searches and focus only on builds relevant to staging or production environments. **If I run list_builds and receive an error, what does that usually mean?** An error often means the provided PAT lacks build history read permissions. You might need to check your token scope or ensure the project ID used in the query is accurate for the intended build. **Does running list_work_items frequently across many projects cause rate limits?** The MCP manages standard API call throttling, but excessive requests in a short period could trigger limits. For large-scale data retrieval, it's better to batch your work item queries or schedule them. **Can I see if a build pipeline failed via the AI?** Yes! Use the `list_builds` tool and provide the Project ID. Your agent will retrieve the history of recent executions, including their final status (succeeded, failed, inProgress). **How do I list the Git repositories for a project?** Run the `list_repositories` query with your Project ID. The agent will return all Git repositories associated with that project in your Azure DevOps account. **Is it possible to see recent bugs or tasks assigned to a project?** Absolutely. Use the `list_work_items` tool. Your agent will retrieve a list of recent work items, including bugs, tasks, and stories, for the specified project.