Azure DevOps (ADO) vs RFix
A side-by-side look at the Azure DevOps (ADO) and RFix 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 declaredR
RFixDeveloper Tools · Remote HTTP/SSECreate RF signal projects from prompts, inspect graphs, and export IQ data.38FairAuth: no auth requiredVerdict: choose Azure DevOps (ADO) for developer tools work as a local process; choose RFix for developer tools over a hosted endpoint. 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.
RChoose RFix when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Azure DevOps (ADO) | R RFix |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 55/100 · Good | 38/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,068 | — |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Azure DevOps (ADO) | View RFix |
Tools & capabilities
Azure DevOps (ADO) tools
No tool names declared yet. Check the project README from the listing page.
RFix tools
No tool names declared yet. Check the project README from the listing page.
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"
]
}
}
}
RFix
{
"mcpServers": {
"rfix": {
"command": "npx",
"args": [
"-y",
"rfix"
]
}
}
}
Frequently asked questions
Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. RFix belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Azure DevOps (ADO) for developer tools work and RFix 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. RFix has no declared pricing — check the project's own site. 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 rfix 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,068 GitHub stars. RFix has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.