Azure DevOps (ADO) vs Uiverify
A side-by-side look at the Azure DevOps (ADO) and Uiverify 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 Uiverify 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 Uiverify when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
UIVERIFY_API_KEY.
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 | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | UIVERIFY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,062 | 23 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Azure DevOps (ADO) | View Uiverify |
Tools & capabilities
Azure DevOps (ADO) tools
No tool names declared yet. Check the project README from the listing page.
Uiverify 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"
]
}
}
}
Uiverify
{
"mcpServers": {
"uiverify": {
"command": "npx",
"args": [
"-y",
"uiverify"
],
"env": {
"UIVERIFY_API_KEY": "YOUR_UIVERIFY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. Uiverify belongs to Developer Tools and uses a local stdio subprocess. Pick Azure DevOps (ADO) for developer tools work and Uiverify 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. Uiverify has no declared pricing — check the project's own site. 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 uiverify 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,062 GitHub stars. Uiverify has 48/100 (Fair) with 1 views, 0 installs and 23 GitHub stars.