Connect Azure DevOps with Unblocked to give AI agents codebase context

Azure DevOps repositories describe the current system, while pull requests retain review context across projects. Unblocked makes both available in one research path, so an agent can answer implementation questions with the change history and project evidence attached.

Azure DevOps context doesn’t live alone. Unblocked links pull requests and their discussions to the code they touch, then combines them with your docs, tickets, and conversations from every other connected source. Instead of raw search results, agents and developers get one reconciled answer with Azure DevOps sources cited.

Once connected, any MCP-compatible coding agent — Claude Code, Cursor, Windsurf, GitHub Copilot, Codex — can pull this context through a single Unblocked MCP server connection.

What you get

• Repository context — Unblocked indexes your source code across your Azure DevOps projects and keeps it in sync as you push changes. The default branch is the source of truth.
• Pull request history — Every pull request, its review comments, and merge decisions become searchable context. Agents can reference past PRs to understand why code works the way it does.
• Project-wide coverage — Connect a project and choose which repositories to index; Unblocked preselects repos active in the last 6 months and can auto-ingest new ones.
• Cross-source synthesis — Azure DevOps data is combined with Slack threads, Jira tickets, Confluence docs, and Sentry errors into a single knowledge graph.

Need screenshots or troubleshooting?This is a concise connection summary. Follow the complete setup guide ↗

Prerequisites

• An Unblocked account on the Enterprise plan (Azure DevOps requires the Enterprise plan).
• Third-party application access via OAuth enabled on your Azure DevOps organization (Organization Settings → Policies).
• Azure DevOps Project Admin access to select projects and repositories, plus a Project Collection Administrator to add the required bot account.
• An MCP-compatible coding agent (Claude Code, Cursor, Windsurf, etc.) to use the context in your editor.

Step 1: Connect Azure DevOps to Unblocked

1. In Azure DevOps, open Organization Settings → Policies and turn on Third-party application access via OAuth.
2. In Unblocked, navigate to Team Settings → Data Sources and select Azure DevOps, then authorize the Unblocked app (sign in to Azure DevOps if prompted).
3. Select the project you want Unblocked to use.
4. Choose the repositories to index — Unblocked preselects repos active in the last 6 months; forks and archived repos are excluded — then click Save and Continue.

Step 2: Install the Unblocked MCP server

On macOS, one command auto-detects and configures your supported agents (Claude Code, Cursor, Windsurf, GitHub Copilot, Codex, VS Code):

The install script supports macOS only. On Windows or Linux, add the server manually using the configuration below, or follow the manual install guide ↗.

claude mcp add -s user --transport http unblocked https://getunblocked.com/api/mcpsse

{
  "mcpServers": {
    "unblocked": {
      "url": "https://getunblocked.com/api/mcpsse"
    }
  }
}

https://getunblocked.com/api/mcpsse

To give Claude Code, Cursor, GitHub Copilot, Codex, or another MCP-compatible AI coding agent access to Azure DevOps context, connect Azure DevOps to Unblocked and add the single Unblocked MCP server to your agent.

Unblocked acts as the MCP context layer for your Azure DevOps data, searching repositories, pull requests, code history alongside your other connected sources and returning cited results through these tools:

• context_researchMulti-source research across your Azure DevOps repositories, pull requests, docs, and messaging. Returns a synthesized answer with citations, so agents understand not just what the code does but why it changed.
• context_get_urlsFetches the full content behind Azure DevOps pull request and file URLs your agent encounters — plus Jira, Linear, Notion, Confluence, Slack, and more.

Questions you (or your agent) can ask Unblocked about your Azure DevOps data:

• Why was the authentication flow refactored, and which pull request introduced it?
• What decisions were made about the database migration approach?
• Which pull requests have touched the billing service in the last 30 days?
• What did reviewers raise on the last PR to the platform repository?