MCP Server Azure Devops vs Zambo
A side-by-side look at the MCP Server Azure Devops and Zambo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Azure Devops for version control work as a local process; choose Zambo for version control. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Azure Devops when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
AZURE_DEVOPS_ORG_URL, AZURE_DEVOPS_PAT. - You want tools like
get_me, list_organizations, list_projects.
Choose Zambo when
- You need dedicated capabilities in the Version Control domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 67/100 · Great | 39/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | other | No auth required |
| Pricing | Free | Free |
| Required env vars | AZURE_DEVOPS_ORG_URLAZURE_DEVOPS_PAT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 397 | — |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 33 | Not listed |
| Full listing | View MCP Server Azure Devops | View Zambo |
Tools & capabilities
MCP Server Azure Devops tools 33
get_meGet details of the authenticated user (id, displayName, email) (Azure DevOps Services only)list_organizationsList all accessible organizations (Azure DevOps Services only)list_projectsList all projects in an organizationget_projectGet details of a specific projectget_project_detailsGet comprehensive details of a project including process, work item types, and teamslist_repositoriesList all repositories in a projectget_repositoryGet details of a specific repositoryget_repository_detailsGet detailed information about a repository including statistics and refsget_file_contentGet content of a file or directory from a repositoryget_repository_treeList a repository's file tree from any path and depthcreate_branchCreate a new branch from an existing onecreate_commitCommit multiple file changes to a branch using unified diffs or search/replace instructions- +21 more on the listing page
Zambo 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.
MCP Server Azure Devops
{
"mcpServers": {
"tiberriver256-mcp-server-azure-devops": {
"command": "npx",
"args": [
"-y",
"@tiberriver256/mcp-server-azure-devops"
],
"env": {
"AZURE_DEVOPS_ORG_URL": "YOUR_AZURE_DEVOPS_ORG_URL_HERE",
"AZURE_DEVOPS_PAT": "YOUR_AZURE_DEVOPS_PAT_HERE"
}
}
}
}
Zambo
No confirmed install command for Zambo yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Server Azure Devops is categorized under Version Control and uses a local stdio subprocess. Zambo belongs to Version Control and uses an install path we have not confirmed yet. Pick MCP Server Azure Devops for version control work and Zambo for version control.
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. Zambo has no confirmed install command yet — follow its own setup instructions.
MCP Server Azure Devops is listed as free. Auth: other. Zambo 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 tiberriver256-mcp-server-azure-devops and zambo-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Azure Devops has a quality signal of 67/100 (Great) with 4 views, 0 installs and 397 GitHub stars. Zambo has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.