Skip to content

Azure DevOps MCP connector

The Azure DevOps connector brings pull requests, reviewers, branch policy configurations and work item states into Claude, ChatGPT, Cursor and Microsoft Copilot through Elaichi, so everyone asks in plain language and works inside their own Azure DevOps access.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Which pull requests are still waiting on a reviewer?

Working in Azure DevOps with Elaichi

  • List all Azure DevOps pull requests
  • Get single Azure DevOps pull request by ID
  • List all Azure DevOps pull request reviewers
Ask anything…
Governance / Audit log Last 24 hours
Azure DevOps List all Azure DevOps pull request reviewers Emily Carter · ChatGPT · 9:41 AM Done
Azure DevOps Get single Azure DevOps pull request by ID Emily Carter · ChatGPT · 9:41 AM Done
Azure DevOps List all Azure DevOps pull requests Emily Carter · ChatGPT · 9:41 AM Done
Azure DevOps List all Azure DevOps policy configurations Megan Brooks · Claude · 9:38 AM Done
Azure DevOps Get single Azure DevOps policy configuration by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Azure DevOps to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Azure DevOps MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Azure DevOps MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Azure DevOps MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Azure DevOps MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Azure DevOps MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Azure DevOps to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Azure DevOps through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Azure DevOps is logged.

  • Engineering

    See which pull requests are still open

    Ask for the open pull requests across a project and get the list back without opening Azure DevOps. Pull up one pull request by number to check its title, branch and status before standup.

  • Engineering managers

    Find out who is reviewing what

    List the reviewers on any pull request and spot the ones waiting on a single person. Ask which pull requests have no reviewer yet and chase them before the day ends.

  • Release management

    Check branch policies before a release

    Pull the policy configurations on a repository and confirm the required reviewer and build checks are in place. Open one policy by ID when something in the release checklist looks off.

  • Security

    Confirm review rules match the standard

    Review every policy configuration in Azure DevOps against your sign-off standard and flag any branch that lets code in with fewer approvals than it should. Do it before an audit instead of after.

  • Project management

    Know which states a work item can take

    Look up the work item states for a project so a new board or report uses the right names. Explain to a new team member what New, Active and Resolved actually mean in your process.

  • Project management

    Clear out a duplicate work item

    Give the ID of a duplicate or mistaken work item and have it deleted from Azure DevOps, with the action logged under your name.

Try asking

  • “Which pull requests are still waiting on a reviewer?”
  • “Show me the branch policies on the main repository.”
  • “Who is reviewing pull request 4821?”

See all 7 Azure DevOps tools →

What connecting Azure DevOps gets you

6 screens from Elaichi, each doing one job for your Azure DevOps account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which pull requests are still waiting on a reviewer?

Show me the branch policies on the main repository.

Who is reviewing pull request 4821?

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about pull requests and get live answers.

Type a plain question and Elaichi's agent reads live Azure DevOps pull requests and policies.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint brings Azure DevOps to every client.

Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
Delete a Azure DevOps work item by ID Delete Deletes a work item: it goes to the project's recycle bin and can be restored (destroy is not sent).
List all Azure DevOps pull requests List List pull requests in a Git repository. Defaults to active PRs; pass searchCriteria.status=all for every PR.
Get single Azure DevOps pull request by ID Get Get a pull request by ID within a project.
List all Azure DevOps pull request reviewers List List reviewers on a pull request with their vote (10 approved, 5 approved with suggestions, 0 no vote, -5 waiting for author, -10 rejected).
List all Azure DevOps policy configurations List List branch policy configurations (required reviewers, minimum approvers, build validation) in a project.

Tool catalog

7 Azure DevOps tools, no code to write.

Pull requests, reviewers, policy configurations and work item states, ready without custom code.

ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

Azure DevOps · pull requests and reviewers

Azure DevOps starter 18 Mar 4, 2026

Release management toolbox

Azure DevOps · branch policies and merges

— 9 Mar 2, 2026

Platform toolbox

Azure DevOps · policy configurations

— 24 Feb 27, 2026

Project management toolbox

Azure DevOps · work item states

Azure DevOps starter 6 Feb 19, 2026

Security toolbox

Azure DevOps · review and policy checks

— 31 Jan 30, 2026

QA toolbox

Azure DevOps · work item states and pull requests

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Azure DevOps toolbox.

Engineering sees pull requests, release managers see policies, each toolbox scoped to one team.

ElaichiConnections
Connection Scope Status Access
AZ

Azure DevOps (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
AZ

Azure DevOps (Mobile)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
AZ

Azure DevOps (Release)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
AZ

Azure DevOps (Security)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
AZ

Azure DevOps (QA)

Connected by Ryan Hayes

Personal • Active Not shared
AZ

Azure DevOps (Project office)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one Azure DevOps connection, never a credential.

One person connects, teams and members work through it, and nobody else sees a token.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Azure DevOps Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Azure DevOps Work items Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Azure DevOps Work items List Toolbox

Audit log

Every Azure DevOps call is logged by name.

When, who, what happened and which pull request or work item, in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Azure DevOps digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch work items

    Azure DevOps

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Azure DevOps

    Queued

Workflows

A schedule starts the pull request digest.

Open Azure DevOps pull requests are fetched, grouped, drafted into a digest, approved, then posted back.

Azure DevOps health

Refreshed 4 minutes ago · every 15 minutes · from the work items collection

Live

Work items

1,284 ↓ 12%

Pull requests

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Work items created

Last 14 days

By team

Share of activity

Platform 34%

Mobile 27%

Release 21%

Security 18%

Collections and dashboards

Azure DevOps health, computed without a model.

Four metrics, 14 days of pull requests opened and a team breakdown, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Azure DevOps

All three can connect Azure DevOps to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Azure DevOps, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Azure DevOps tools Allow or restrict single Azure DevOps tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Azure DevOps call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Azure DevOps tools for your AI agents

7 tools are ready to call through Elaichi's MCP endpoint the moment you connect Azure DevOps, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Azure DevOps to Claude?

Connect Azure DevOps in Elaichi by signing in with the Microsoft account you already use for Azure DevOps and approving access, which takes about a minute. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi and Azure DevOps is ready.

Does Azure DevOps work with ChatGPT and Cursor as well as Claude?

Yes. The Azure DevOps connector sits behind one Elaichi endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent all use that same address. You connect Azure DevOps once in Elaichi and every client picks it up.

What can an AI agent actually do with my Azure DevOps data?

With Azure DevOps connected, an agent can list open pull requests, open a single pull request by number, show who is reviewing it, list the branch policy configurations on a repository and look up the work item states a project uses. It can also delete a work item when you give it the ID. Short, concrete asks such as "who is reviewing pull request 4821" work better than long paragraphs.

Does connecting Azure DevOps give the AI access to every project and repository?

No. Every call to Azure DevOps runs as the person who signed in, so an agent sees only the projects, repositories and pull requests that person can already see in Azure DevOps. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what Azure DevOps already allows.

Can my team share one Azure DevOps connection?

Yes. One person connects Azure DevOps in Elaichi and shares the connection with a team, and nobody else ever handles a token or credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every pull request lookup or work item deletion.

Can I stop an agent from deleting work items in Azure DevOps?

Yes. In Elaichi you restrict actions one at a time, such as deleting a work item in Azure DevOps, and the restriction applies to a role or to one person. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.

What happens to an Azure DevOps connection when someone leaves?

Offboarding a person in Elaichi ends their Azure DevOps access through every client at once. If they shared the Azure DevOps connection with a team, it keeps working for everyone else. If you ever want it gone entirely, disconnecting Azure DevOps once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

Does the Azure DevOps MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Azure DevOps is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Azure DevOps?

Yes. Both let Claude, ChatGPT or Cursor use Azure DevOps. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Azure DevOps call.

How is Elaichi different from Composio for Azure DevOps?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Azure DevOps: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Azure DevOps in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot