Ext Ops Panel
Open dashboard
Comparison

DevHelm MCP Server vs Agent Mesh

DevHelm MCP Server is an MCP server published by devhelmhq. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Agent Mesh is an MCP server published by google. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceDevHelm MCP ServerAgent Mesh
Official MCP Registry Listed
Version: 1.0.2
Downloads/month (PyPI): 128
Downloads/week (PyPI): 48
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.2.0
Forks (GitHub): 200
Stars (GitHub): 1 186
Not marked · First seen
PyPI (MCP servers) Listed
Version: 1.8.0
Downloads/month (PyPI): 128
Downloads/week (PyPI): 48
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

DevHelm MCP Server vs Agent Mesh
FactDevHelm MCP ServerAgent Mesh
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1 (worse)1 186 (better)
Forks (GitHub) (differs)0 (worse)200 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (devhelm-mcp-server)On your machine (@agentmesh-p2p/sdk)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/devhelmhq/mcp-servergithub.com/google/agentmesh
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-02

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

DevHelm MCP Server

In its own words, on Official MCP Registry:

Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm

Agent Mesh

In its own words, on Official MCP Registry:

Discover and call remote MCP tools as your own authenticated Agent Mesh member.

How to run each

DevHelm MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DEVHELM_API_TOKEN=<YOUR_DEVHELM_API_TOKEN>" --transport stdio devhelm-mcp-server -- uvx devhelm-mcp-server

Requires: DEVHELM_API_TOKEN (secret)

Agent Mesh As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTMESH_BOOTSTRAP_TOKEN_PATH=<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>" --env "AGENTMESH_CONTROL_PLANE_URL=<YOUR_AGENTMESH_CONTROL_PLANE_URL>" --env "AGENTMESH_JWT_PATH=<YOUR_AGENTMESH_JWT_PATH>" --transport stdio agentmesh -- npx -y @agentmesh-p2p/sdk

Requires: AGENTMESH_BOOTSTRAP_TOKEN_PATH (secret), AGENTMESH_CONTROL_PLANE_URL, AGENTMESH_JWT_PATH (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only DevHelm MCP Server asks for

  • DEVHELM_API_TOKEN (secret)

Only Agent Mesh asks for

  • AGENTMESH_BOOTSTRAP_TOKEN_PATH (secret)
  • AGENTMESH_CONTROL_PLANE_URL
  • AGENTMESH_INSECURE_CONTROL_PLANE
  • AGENTMESH_JWT_PATH (secret)
  • AGENTMESH_STATE_DIR

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: DevHelm MCP Server · What it can do: Agent Mesh · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built