Azure DevOps MCP server

What the model can do

Azure DevOps Services: projects, repositories, pull requests with reviewers and comment threads, work items by query or id with their discussion, builds and pipelines; can also create, change, comment on or delete work items, open, vote on, comment on, abandon or complete pull requests, run a pipeline on a branch and cancel a build when you ask.

Reads

• azuredevops_projectsList the projects in the Azure DevOps organization: name, id, description, state and visibility.
• azuredevops_repositoriesGit repositories in a project: name, id, default branch, size, whether disabled or a fork, and the browsable URL.
• azuredevops_pull_requestsPull requests in a project, or in one repository: title, status (active, completed, abandoned), draft flag, author, dates, source and target branch…
• azuredevops_pull_requestOne pull request in full: description, reviewers and votes, merge status, linked work items, and its comment threads (file, line, status…
• azuredevops_work_itemsWork items (user stories, bugs, tasks, epics, features…) matching filters, up to 200: id, type, title, state, assigned to, priority, iteration, area…
• azuredevops_work_itemOne work item by id in full: every list field plus the description, acceptance criteria or repro steps (HTML stripped)…
• azuredevops_buildsBuilds (pipeline runs) in a project, newest queued first: build number, pipeline, status (inProgress, completed, notStarted, cancelling, postponed)…
• azuredevops_pipelinesPipelines (build definitions) in a project: id, name, folder, type (yaml or designer) and URL.

Acts, when you ask

These change something in Azure DevOps. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• azuredevops_comment_work_itemAdds a comment to an Azure DevOps work item's discussion, under the name of whoever owns the personal access token, notifying the item's followers.
• azuredevops_create_work_itemCreates a work item in an Azure DevOps project (a Bug, Task, User Story, Product Backlog Item, Epic…
• azuredevops_update_work_itemChanges fields on one Azure DevOps work item: title, state (e.g. Active, Resolved, Closed, Done), reason, assignee (an empty string unassigns)…
• azuredevops_delete_work_itemDeletes an Azure DevOps work item to the project's recycle bin, from which a project administrator can restore it…
• azuredevops_create_pull_requestOpens a pull request in an Azure DevOps repository from source_branch into target_branch, under the token owner's name.
• azuredevops_vote_on_pull_requestCasts the token owner's vote on an Azure DevOps pull request: approve, approve_with_suggestions, wait_for_author, reject, or reset to no vote.
• azuredevops_comment_on_pull_requestStarts a comment thread on an Azure DevOps pull request under the token owner's name, on the change as a whole or, with file_path and line…
• azuredevops_update_pull_requestChanges an Azure DevOps pull request's title or description, or abandons it (status abandoned) or reactivates an abandoned one (status active).
• azuredevops_complete_pull_requestCompletes (merges) an Azure DevOps pull request into its target branch, which cannot be undone from here…
• azuredevops_run_pipelineStarts a run of an Azure DevOps pipeline on the named branch, which runs whatever that pipeline does (tests, builds…
• azuredevops_cancel_buildCancels a queued or running Azure DevOps build (pipeline run).

Connect it

First connect Azure DevOps on Dashboard → Connections, then add Memtro to your client once. The Azure DevOps tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Azure DevOps connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which pull requests into main are waiting for a reviewer vote?
• › What did reviewers say on PR 412 in the web-platform repo?
• › Show me the open bugs in Sprint 42 assigned to Priya Sharma
• › Did any builds fail on main today, and which pipeline?
• › Add a comment to work item 8831 saying the fix shipped in release 3.14

Questions

Is this an official Azure DevOps MCP server?

No. It is Memtro's MCP server with Memtro's Azure DevOps connector behind it: the connector reads Azure DevOps through its API with the credentials you connect on Dashboard → Connections, and Azure DevOps publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Azure DevOps?

Only when you ask, and only what it has been granted: add a comment to a work item's discussion; create a work item (bug, task, user story...) with title, description, assignee, priority, area, iteration and tags; change a work item's title, state, assignee, priority, area, iteration, tags or description; delete a work item to the recycle bin; open a pull request from one branch into another; approve, reject or otherwise vote on a pull request as the token's owner; start a comment thread on a pull request, on the whole change or a line of a file; retitle, redescribe, abandon or reactivate a pull request; complete (merge) a pull request; run a pipeline on a named branch; cancel a running build. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server