Jev agent tools vs Azure DevOps (ADO)

A side-by-side look at the Jev agent tools 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.

Jev agent tools logoJev agent toolsDeveloper Tools · Local subprocess (stdio)Evidence-oriented code questions, diff review and test selection via a Jev endpoint.47FairAuth: 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 Jev agent tools 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?

Jev agent tools logoChoose Jev agent tools when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: JEV_TOOLS_URL, JEV_TOOLS_API_KEY.
Explore Jev agent tools

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.

SpecJev agent tools logoJev agent tools
A
Azure DevOps (ADO)
CategoryDeveloper ToolsDeveloper Tools
Quality signal47/100 · Fair55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsJEV_TOOLS_URLJEV_TOOLS_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars92,068
Directory activity 0 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Jev agent tools 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.

Jev agent tools

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "jev-agent-tools": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "jev-agent-tools",
        "jev-agent-tools-mcp"
      ],
      "env": {
        "JEV_TOOLS_URL": "YOUR_JEV_TOOLS_URL_HERE",
        "JEV_TOOLS_API_KEY": "YOUR_JEV_TOOLS_API_KEY_HERE"
      }
    }
  }
}

Azure DevOps (ADO)

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

Frequently asked questions

Jev agent tools 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 Jev agent tools 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.

Jev agent tools has no declared pricing — check the project's own site. 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 jev-agent-tools and azure-devops-ado as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Jev agent tools has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 9 GitHub stars. Azure DevOps (ADO) has 55/100 (Good) with 6 views, 0 installs and 2,068 GitHub stars.