Bring Ci Cd
to Cursor
Learn how to connect Azure DevOps to Cursor and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Azure DevOps MCP Server?
Connect your Azure DevOps account to any AI agent and simplify how you manage your software development lifecycle, track work items, and monitor pipelines through natural conversation.
What you can do
- Project Oversight — List all projects in your organization and retrieve detailed metadata and configurations.
- Work Item Tracking — List and query recent tasks, bugs, and user stories to manage your team's backlog.
- Git Repository Control — Query all Git repositories within a project to monitor code storage.
- Pipeline Monitoring — List CI/CD pipelines and retrieve the history of recent build executions and statuses.
- Team Coordination — List project teams to understand organizational structure and distribution.
- Operational Status — Fetch real-time metadata for projects and work items directly via AI commands.
How it works
1. Subscribe to this server
2. Enter your Azure DevOps Organization and Personal Access Token (PAT)
3. Start managing your DevOps ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Developers & Engineers — quickly check pipeline statuses and verify work item details via simple AI queries.
- DevOps Specialists — monitor build history and manage repositories directly from the workspace.
- Product Owners — get instant bird's-eye views of work item progress and project health via the AI assistant.
Built-in capabilities (6)
List recent builds
List CI/CD pipelines
List teams in a project
List Azure DevOps projects
List Git repositories
List recent work items
Why Cursor?
Cursor's Agent mode turns Azure DevOps into an in-editor superpower. Ask Cursor to generate code using live data from Azure DevOps and it fetches, processes, and writes. all in a single agentic loop. 6 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Azure DevOps in Cursor
Azure DevOps and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Azure DevOps to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Azure DevOps in Cursor
The Azure DevOps MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Azure DevOps for Cursor
Every tool call from Cursor to the Azure DevOps MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.