Azure DevOps MCP. Track build status and manage work items from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Azure DevOps connects your AI client directly to your entire software development lifecycle. You can list projects, track recent work items, view Git repositories, and monitor CI/CD pipelines using natural conversation.
It gives your agent full visibility into build history, project status, and team structure.
What your AI agents can do
List builds
Retrieves a list of recent CI/CD build executions and their status.
List pipelines
Retrieves a list of configured CI/CD pipelines within the organization.
List project teams
Retrieves a list of teams that belong to a specific project.
The agent retrieves a list of all projects within your entire Azure DevOps organization.
The agent queries and returns a list of the most recent tasks, bugs, and user stories assigned to a project.
The agent retrieves a list of all Git repositories contained within a specified project.
The agent retrieves a list of all continuous integration/continuous delivery pipelines configured for a project.
The agent retrieves the build history, including the status and triggers, for recent CI/CD build executions.
The agent fetches a list of teams that are currently assigned or active within a specified project.
The agent pulls real-time, specific data points about projects or work items directly upon command.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Azure DevOps MCP Server: 6 Tools for Dev Lifecycle
Use these tools to query and manage every part of your software development process, from project listing to build history.
019dd0bflist builds
Retrieves a list of recent CI/CD build executions and their status.
019dd0bflist pipelines
Retrieves a list of configured CI/CD pipelines within the organization.
019dd0bflist project teams
Retrieves a list of teams that belong to a specific project.
019dd0bflist projects
Retrieves a list of all available projects in the Azure DevOps organization.
019dd0bflist repositories
Retrieves a list of Git repositories for a given project.
019dd0bflist work items
Retrieves a list of recent work items, including bugs, tasks, and stories.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Azure DevOps, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Azure DevOps connects your AI client right into your whole software development lifecycle. You can list projects, track work items, view Git repos, and monitor CI/CD pipelines just by talking to your agent. It gives your agent full visibility into build history, project status, and team structure.
list_projects gives you a list of every project in your entire Azure DevOps organization. list_work_items queries and returns a list of the most recent tasks, bugs, and user stories assigned to a project. list_repositories retrieves a list of all Git repositories contained within a specified project. list_pipelines retrieves a list of all continuous integration/continuous delivery pipelines configured for a project. list_builds retrieves the build history, including the status and triggers, for recent CI/CD build executions. list_project_teams fetches a list of teams that are currently assigned or active within a specified project.
You can also pull real-time, specific data points about projects or work items directly upon command.
How Azure DevOps MCP Works
- 1 Subscribe to the server and enter your Azure DevOps Organization and Personal Access Token (PAT).
- 2 Your AI client connects to the server and executes a tool (e.g.,
list_pipelines). - 3 The server calls the Azure DevOps API, returns the data, and your agent uses it to answer the question.
The bottom line is: you manage your whole DevOps ecosystem from your agent, no UI clicks required.
Who Is Azure DevOps MCP For?
The DevOps Specialist who's tired of clicking through multiple dashboards to see if a build failed. The Product Owner who needs an instant, high-level view of project health. Or the Developer who just wants to check a work item status without logging into the portal.
Monitors build history, manages repositories, and tracks pipeline failures directly from their workspace.
Gets a quick, bird's-eye view of work item progress and overall project health via simple AI queries.
Checks pipeline statuses and verifies work item details instantly via simple AI queries.
What Changes When You Connect
- See the full project structure by running
list_projectsto get a list of all active teams and codebases in your organization. - Get an immediate status check on your deployment process. Use
list_pipelinesto see all configured CI/CD pipelines and their last run status. - Stay ahead of bugs. Use
list_work_itemsto pull the latest bugs and stories, knowing exactly what needs to be prioritized in the backlog. - Verify code location instantly.
list_repositoriesgives you a clear list of all Git repos in a project without navigating the web UI. - Know who's running what.
list_project_teamsshows which teams are assigned to a project, so you know who to ping when a build fails. - Avoid context switching. By using tools like
list_buildsandlist_work_items, you pull all necessary status data into your chat window instantly.
Real-World Use Cases
Debugging a failed build
The build failed, and you need to know what broke. You ask your agent to run list_builds for the 'Mobile App' project. The agent checks the status, sees the last build failed, and then runs list_work_items to see if there's a related bug logged, solving the problem without leaving the chat.
Auditing project scope
You need to know if the new hire can see all the relevant code. You ask the agent to run list_projects first, then list_repositories for the target project. This verifies the scope of code access and lets you confirm the correct team structure using list_project_teams.
Checking release readiness
The Product Owner needs to know if the next feature is ready. They ask the agent to check list_pipelines to ensure the latest build succeeded, and then run list_work_items to confirm the associated user story is marked as 'Ready for Review'.
Mapping dependencies
You're onboarding a new developer and need to see their scope. You ask the agent to run list_projects to get the organization overview, then use list_repositories and list_work_items to define the exact boundaries of their work.
The Tradeoffs
Manual Dashboard Diving
Logging into the Azure DevOps portal, navigating to 'Pipelines,' checking the build history, then switching tabs to 'Work Items' to find the related bug ID, and finally opening the 'Repositories' tab to confirm the branch name.
→
Ask your agent to run list_pipelines and list_work_items simultaneously. It gives you the build status and the bug ID—all in one chat response, eliminating the need to switch tabs.
Guessing Build Status
Seeing a build ID number and having to manually search the build history page to determine if it was 'Succeeded' or 'Failed' and when it happened.
→
Just ask the agent to run list_builds. It pulls the status, the date, and the trigger source directly into the conversation.
Ignoring Project Boundaries
Assuming a work item relates to a specific repo without verifying the project scope first, leading to searching in the wrong code repository or wrong team structure.
→
Always start by running list_projects to confirm the correct project boundary, then use list_repositories to confirm the relevant code location.
When It Fits, When It Doesn't
Use this server if your bottleneck is visibility across different Azure DevOps domains (code, tasks, deployments). The key is when you need to correlate data points—for example, linking a specific bug found via list_work_items to the exact build failure via list_builds. Don't use this if your primary need is deep, specialized data governance, like managing user permissions or complex resource allocation; those require dedicated Azure services. If you just need to view a single, simple list (e.g., 'what are all my projects?'), the basic Azure API might suffice. But if you need to ask questions that synthesize information across projects, work items, and pipelines, this is what you need.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Azure DevOps. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 6 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Tracking project status means jumping between 5 different Azure tabs.
Today, checking the health of a feature requires a manual, multi-step process. You start at the Pipelines tab to check the latest build. If that passed, you click over to the Work Items tab to ensure the story is marked done. Then you jump to the Repositories tab to confirm the correct branch. This is clicking, copy-pasting, and context switching.
With the Azure DevOps MCP Server, you just ask your agent: 'What's the status of the 'Dark Mode' feature?' It runs `list_pipelines`, `list_work_items`, and `list_repositories` and gives you a single, synthesized answer, pointing out the build status and the story ID—no tabs involved.
List Work Items: Track bugs and stories directly from chat.
You no longer have to navigate to the Work Items board, filter by status, and then scroll through pages of tasks just to find the latest bug report. You simply ask the agent for 'recent bugs' and get a clean, actionable list.
It’s instant project health data. You get the list of recent items and their IDs, right in your conversation. That's the difference.
Common Questions About Azure DevOps MCP
How do I use the list_builds tool to check the status of a project? +
You don't call the tool directly. You ask your agent to 'What is the status of the latest build for the 'Mobile App' project?'. The agent runs list_builds and presents the status, ID, and time directly.
Can list_work_items show me only the bugs, not the tasks? +
Yes. You need to specify the type of work item in your prompt. For example, 'Show me only the recent bugs for the Marketing project.' The agent handles the filtering.
Do I need to list_projects before I can use list_repositories? +
It's best practice. First, run list_projects to get the organization list. Then, specify the project name when asking for repositories using list_repositories.
Does list_pipelines track everything, or just the main ones? +
The tool lists all configured CI/CD pipelines. You can ask for a specific pipeline name, or ask the agent to list them all first to see your options.
How do I check the team structure using list_project_teams? +
Just ask the agent to 'List the project teams for [Project Name]'. It pulls the team roster and structure right into your chat.
What information does list_work_items provide about a specific work item? +
It provides key metadata for the item, including its type, status, and creation date. You can then ask for specific details, like the assigned developer or the priority level, to narrow down the results.
Is there a way to use list_repositories to filter by branch name? +
While list_repositories lists all available Git repos, you can refine the search by referencing the project name or the desired repository name in your prompt. The underlying API supports specific filtering parameters.
If I run list_pipelines, how do I determine which pipeline is most up-to-date? +
The output includes the last run timestamp and the build status for each pipeline. You just need to ask your agent to sort the results by the 'last run' date to see the most active ones.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Salesmate
Automate sales CRM via Salesmate — manage contacts, track deals, and log activities directly with AI.
Ele.me Open Platform / 饿了么
China's massive food delivery API — manage shops, process orders, and track deliveries via AI.
Sproof
Manage digital signatures, documents, and contacts on Sproof with AI agents.
You might also like
Plivo
Equip AI with native telecom powers. Send SMS, manage SIP trunks, and audit voice calls autonomously.
Emarsys
Equip your AI agent to manage email campaigns, track contact lists, and monitor automation programs via the Emarsys API.
Assembly
Manage Assembly clients, companies, workspaces, and notes.