Azure DevOps (ADO) vs Codegraphcontext

A side-by-side look at the Azure DevOps (ADO) and Codegraphcontext 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
Codegraphcontext logoCodegraphcontextDeveloper Tools · Local subprocess (stdio)An MCP server that indexes local code into a graph database to provide context to AI assistants with a graphical code visualizations for humans.59GoodAuth: no auth required

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

Codegraphcontext logoChoose Codegraphcontext when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Codegraphcontext

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
Azure DevOps (ADO)
Codegraphcontext logoCodegraphcontext
CategoryDeveloper ToolsDeveloper Tools
Quality signal55/100 · Good59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,0604,301
Directory activity 6 views 0 installs 0 upvotes 5 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.

Codegraphcontext 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"
      ]
    }
  }
}

Codegraphcontext

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shashankss1205-codegraphcontext": {
      "command": "uvx",
      "args": [
        "kuzu"
      ]
    }
  }
}

Frequently asked questions

Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. Codegraphcontext belongs to Developer Tools and uses a local stdio subprocess. Pick Azure DevOps (ADO) for developer tools work and Codegraphcontext 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. Codegraphcontext is listed as free. Auth: no auth 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 shashankss1205-codegraphcontext 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,060 GitHub stars. Codegraphcontext has 59/100 (Good) with 5 views, 0 installs and 4,301 GitHub stars.