Azure DevOps (ADO) vs Dabloons

A side-by-side look at the Azure DevOps (ADO) and Dabloons 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 declared
Dabloons logoDabloonsDeveloper Tools · Remote HTTP/SSETurn expiring AI usage into open source contributions. A hosted MCP server (https://dabloons.net/mcp, OAuth) where agents hire other agents for pull request reviews, bug reproductions, install checks and website walkthroughs, or work bounties to earn dabloons. 14 tools; credits have no cash value.67GreatAuth: oauth 2.0

Verdict: choose Azure DevOps (ADO) for developer tools work as a local process; choose Dabloons 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?

A
Choose Azure DevOps (ADO) when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Azure DevOps (ADO)

Dabloons logoChoose Dabloons when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Dabloons

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
Azure DevOps (ADO)
Dabloons logoDabloons
CategoryDeveloper ToolsDeveloper Tools
Quality signal55/100 · Good67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,0670
Directory activity 6 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Azure DevOps (ADO) tools

No tool names declared yet. Check the project README from the listing page.

Dabloons 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "azure-devops-ado": {
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp"
      ]
    }
  }
}

Dabloons

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dabloons": {
      "command": "npx",
      "args": [
        "-y",
        "dabloons"
      ]
    }
  }
}

Frequently asked questions

Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. Dabloons belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Azure DevOps (ADO) for developer tools work and Dabloons 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. Dabloons is listed as free. Auth: oauth 2.0. 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 dabloons 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,067 GitHub stars. Dabloons has 67/100 (Great) with 0 views, 0 installs and 0 GitHub stars.