OpenMetadata vs Azure DevOps (ADO)

A side-by-side look at the OpenMetadata 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.

OpenMetadata logoOpenMetadataDeveloper Tools · Local subprocess (stdio)Official OpenMetadata MCP: governed context and business semantics for AI assistants and agents.48FairAuth: 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 OpenMetadata for developer tools work as a local process; 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?

OpenMetadata logoChoose OpenMetadata when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore OpenMetadata

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.

SpecOpenMetadata logoOpenMetadata
A
Azure DevOps (ADO)
CategoryDeveloper ToolsDeveloper Tools
Quality signal48/100 · Fair55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars15,5522,062
Directory activity 1 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

OpenMetadata 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.

OpenMetadata

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openmetadata": {
      "command": "uvx",
      "args": [
        "data-ai-sdk"
      ]
    }
  }
}

Azure DevOps (ADO)

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

Frequently asked questions

OpenMetadata is categorized under Developer Tools and uses a local stdio subprocess. Azure DevOps (ADO) belongs to Developer Tools and uses a local stdio subprocess. Pick OpenMetadata 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.

OpenMetadata 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 openmetadata and azure-devops-ado as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, OpenMetadata has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 15,552 GitHub stars. Azure DevOps (ADO) has 55/100 (Good) with 6 views, 0 installs and 2,062 GitHub stars.