Azure DevOps (ADO) vs Monnet MCP
A side-by-side look at the Azure DevOps (ADO) and Monnet MCP 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 Monnet MCP 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 Monnet MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
monnet_whoami, list_workspaces, get_inbox.
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 | 56/100 · Good |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,066 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 11 |
| Full listing | View Azure DevOps (ADO) | View Monnet MCP |
Tools & capabilities
Azure DevOps (ADO) tools
No tool names declared yet. Check the project README from the listing page.
Monnet MCP tools 11
monnet_whoamiVerify the connection and list the API keys on your accountlist_workspacesList the workspaces you belong toget_inboxFetch your inboxlist_motionsList motions in a workspaceget_motionRead a motion — summary, body, plan, members, commentscreate_motionCreate a new draft motion from a free-form promptupdate_motionUpdate a motion's summary, body, priority, or plancommentPost a comment on a motion (approval-gated, see below)approveApprove a plan steprejectReject a plan step (with an optional reason)ask_monnetAsk Monnet a question on a motion
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"
]
}
}
}
Monnet MCP
{
"mcpServers": {
"mcp-17": {
"command": "npx",
"args": [
"-y",
"@monnet/mcp"
]
}
}
}
Frequently asked questions
Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. Monnet MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Azure DevOps (ADO) for developer tools work and Monnet MCP 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. Monnet MCP 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 mcp-17 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,066 GitHub stars. Monnet MCP has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.