Azure DevOps (ADO) vs MCP Openapi
A side-by-side look at the Azure DevOps (ADO) and MCP Openapi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Azure DevOps (ADO)Developer Tools · Local subprocess (stdio)The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.55GoodAuth: not declaredVerdict: choose Azure DevOps (ADO) for developer tools work as a local process; choose MCP Openapi for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Azure DevOps (ADO) when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose MCP Openapi when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
OPENAPI_BEARER_TOKEN, OPENAPI_API_KEY, OPENAPI_API_KEY_HEADER, OPENAPI_BASIC_USER, OPENAPI_BASIC_PASS. - You want tools like
list_endpoints, call_endpoint.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Azure DevOps (ADO) | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 55/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | OPENAPI_BEARER_TOKENOPENAPI_API_KEYOPENAPI_API_KEY_HEADEROPENAPI_BASIC_USEROPENAPI_BASIC_PASS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,063 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Azure DevOps (ADO) | View MCP Openapi |
Tools & capabilities
Azure DevOps (ADO) tools
No tool names declared yet. Check the project README from the listing page.
MCP Openapi tools 2
list_endpointsReturns all operations grouped by tag with operationIds, methods, paths, and parameterscall_endpointExecutes any operation by `operationId` with path/query/header/body parameters
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Azure DevOps (ADO)
{
"mcpServers": {
"azure-devops-ado": {
"command": "npx",
"args": [
"-y",
"@azure-devops/mcp"
]
}
}
}
MCP Openapi
{
"mcpServers": {
"saurav61091-mcp-openapi": {
"command": "npx",
"args": [
"-y",
"mcp-openapi-runner"
],
"env": {
"OPENAPI_BEARER_TOKEN": "YOUR_OPENAPI_BEARER_TOKEN_HERE",
"OPENAPI_API_KEY": "YOUR_OPENAPI_API_KEY_HERE",
"OPENAPI_API_KEY_HEADER": "YOUR_OPENAPI_API_KEY_HEADER_HERE",
"OPENAPI_BASIC_USER": "YOUR_OPENAPI_BASIC_USER_HERE",
"OPENAPI_BASIC_PASS": "YOUR_OPENAPI_BASIC_PASS_HERE"
}
}
}
}
Frequently asked questions
Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. MCP Openapi belongs to Developer Tools and uses a local stdio subprocess. Pick Azure DevOps (ADO) for developer tools work and MCP Openapi for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Azure DevOps (ADO) is listed as free. MCP Openapi is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add azure-devops-ado and saurav61091-mcp-openapi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Azure DevOps (ADO) has a quality signal of 55/100 (Good) with 6 views, 0 installs and 2,063 GitHub stars. MCP Openapi has 39/100 (Fair) with 4 views, 0 installs and 1 GitHub stars.