Magic Cloud vs Azure DevOps (ADO)

A side-by-side look at the Magic Cloud and Azure DevOps (ADO) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Magic Cloud logoMagic CloudDeveloper ToolsSelf-hosted low-code platform (Docker); its MCP endpoint runs on your own instance, not via npx.41FairAuth: not declared
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

Verdict: choose Magic Cloud for developer tools work; choose Azure DevOps (ADO) 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?

Magic Cloud logoChoose Magic Cloud when

  • You need dedicated capabilities in the Developer Tools domain.
Explore Magic Cloud

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)

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMagic Cloud logoMagic Cloud
A
Azure DevOps (ADO)
CategoryDeveloper ToolsDeveloper Tools
Quality signal41/100 · Fair55/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,2042,062
Directory activity 2 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Magic Cloud tools

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

Azure DevOps (ADO) 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.

Magic Cloud

No confirmed install command for Magic Cloud yet — follow the setup steps linked from its listing page rather than a guessed package name.

Azure DevOps (ADO)

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "azure-devops-ado": {
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp"
      ]
    }
  }
}

Frequently asked questions

Magic Cloud is categorized under Developer Tools and uses an install path we have not confirmed yet. Azure DevOps (ADO) belongs to Developer Tools and uses a local stdio subprocess. Pick Magic Cloud for developer tools work and Azure DevOps (ADO) 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. Magic Cloud has no confirmed install command yet — follow its own setup instructions.

Magic Cloud is listed as free. Azure DevOps (ADO) is listed as free. 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 magic-cloud and azure-devops-ado as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Magic Cloud has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 1,204 GitHub stars. Azure DevOps (ADO) has 55/100 (Good) with 6 views, 0 installs and 2,062 GitHub stars.