Developer · Remote MCP server

Azure DevOps (unofficial remote entry)

Unofficial entry for Microsoft's hosted Azure DevOps MCP server. Not affiliated with Microsoft.

Visit Azure DevOps (unofficial remote entry)'s website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.joachim-aqf/azure-devops
Version
0.1.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-08-11
Updated
2026-08-11
Publisher
joachim-aqf (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/joachim-aqf) · how
Listed under
Azure MCP servers, Azure DevOps MCP servers
Website
learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.dev.azure.com/{organization}X-MCP-Toolsets, X-MCP-Readonly

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Checked
Not requested: URL template placeholder
Checked on
2026-10-05

How the live check works

How to connect Azure DevOps (unofficial remote entry)

Azure DevOps (unofficial remote entry) is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.dev.azure.com/{organization}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The URL contains placeholders to fill in before connecting: {organization}.

The registry entry declares HTTP headers for the connection: X-MCP-Toolsets and X-MCP-Readonly. Clients that accept custom headers set them with the server's URL.

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

Site checks

The website's own root, learn.microsoft.com, was checked for the files that tell AI systems about a site.

FileResult
/llms.txtNo real file found
/.well-known/mcp.jsonNo real file found
/.well-known/ai-plugin.jsonNo real file found
/agents.jsonNo real file found

More developer servers

All 5,152 →
ServerRunsEndpoint or package
AxisCoding agents from Claude Code, Cursor and Codex claim jobs and lock files on one shared board.Remote & Local · HTTP, stdioLive check: sign-in requireduseaxis.dev
Axis Iliad - Codebase Intelligence For Agentic CommerceCodebase intelligence for agents: 152 structured artifacts across 21 programs, one call.Remote · HTTPLive check: ✗ no handshakeaxis-api-6c7z.onrender.com
Axon NeuroAutomataProtein analysis: ESM-2/ESMC embeddings, mutation scoring, landscape scans, ESMFold structure.Remote · HTTPLive check: sign-in requiredmcp.neuroautomata.axonagentic.ai
Azure Boards MCPAzure DevOps Boards work items over MCP (stdio). Requires Bun, org, project, and PAT.Local · stdionpm: azure-board-mcp
Azure DevOps On-PremisesMCP server for on-premises Azure DevOps Server and TFS: repos, pull requests, work items, and wiki.Local · stdioPyPI: mcp-devops-onpremise
Azure FinOps MCP ServerAzure FinOps MCP: cost, budgets, forecasting and optimization for Claude, VS Code and Cursor.Local · stdioPyPI: azure-finops-mcp
Azure IoT HubMCP server for Azure IoT Hub: device registry, twins, methods, jobs, messaging.Local · stdioPyPI: azure-iot-hub-mcp-server
Azure MCP ServerAll Azure MCP tools to create a connection between AI agents and Azure services.Local · stdioNuGet: Azure.Mcp