Azure DevOps (ADO) vs Brilliant Directories MCP

A side-by-side look at the Azure DevOps (ADO) and Brilliant Directories 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 declared
Brilliant Directories MCP logoBrilliant Directories MCPDeveloper Tools · Local subprocess (stdio)Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.49FairAuth: api key required

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

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)

Brilliant Directories MCP logoChoose Brilliant Directories MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Brilliant Directories MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
Azure DevOps (ADO)
Brilliant Directories MCP logoBrilliant Directories MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal55/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,06818
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.

Brilliant Directories MCP 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"
      ]
    }
  }
}

Brilliant Directories MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "brilliant-directories-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "--prefer-online",
        "brilliant-directories-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. Brilliant Directories MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Azure DevOps (ADO) for developer tools work and Brilliant Directories 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. Brilliant Directories MCP has no declared pricing — check the project's own site. Auth: api key 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 azure-devops-ado and brilliant-directories-mcp 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,068 GitHub stars. Brilliant Directories MCP has 49/100 (Fair) with 0 views, 0 installs and 18 GitHub stars.