Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Agent Mesh

by googleversion 0.2.0i★ –iRuns on your computer
Registry nameio.github.google/agentmesh

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: AGENTMESH_CONTROL_PLANE_URL, AGENTMESH_BOOTSTRAP_TOKEN_PATH, AGENTMESH_JWT_PATH

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: AGENTMESH_CONTROL_PLANE_URL, AGENTMESH_BOOTSTRAP_TOKEN_PATH, AGENTMESH_JWT_PATH, AGENTMESH_STATE_DIR, AGENTMESH_INSECURE_CONTROL_PLANE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "agentmesh": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmesh-p2p/sdk"
      ],
      "env": {
        "AGENTMESH_CONTROL_PLANE_URL": "your-value",
        "AGENTMESH_BOOTSTRAP_TOKEN_PATH": "your-value",
        "AGENTMESH_JWT_PATH": "your-value",
        "AGENTMESH_STATE_DIR": "your-value",
        "AGENTMESH_INSECURE_CONTROL_PLANE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add agentmesh --env AGENTMESH_CONTROL_PLANE_URL=your-value --env AGENTMESH_BOOTSTRAP_TOKEN_PATH=your-value --env AGENTMESH_JWT_PATH=your-value --env AGENTMESH_STATE_DIR=your-value --env AGENTMESH_INSECURE_CONTROL_PLANE=your-value -- npx -y @agentmesh-p2p/sdk

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agentmesh": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmesh-p2p/sdk"
      ],
      "env": {
        "AGENTMESH_CONTROL_PLANE_URL": "your-value",
        "AGENTMESH_BOOTSTRAP_TOKEN_PATH": "your-value",
        "AGENTMESH_JWT_PATH": "your-value",
        "AGENTMESH_STATE_DIR": "your-value",
        "AGENTMESH_INSECURE_CONTROL_PLANE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agentmesh": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@agentmesh-p2p/sdk"
      ],
      "env": {
        "AGENTMESH_CONTROL_PLANE_URL": "your-value",
        "AGENTMESH_BOOTSTRAP_TOKEN_PATH": "your-value",
        "AGENTMESH_JWT_PATH": "your-value",
        "AGENTMESH_STATE_DIR": "your-value",
        "AGENTMESH_INSECURE_CONTROL_PLANE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • AGENTMESH_CONTROL_PLANE_URL required env
    Control plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below.
  • AGENTMESH_BOOTSTRAP_TOKEN_PATH secret env
    Absolute path to a bootstrap token file for first enrollment. Set this OR AGENTMESH_JWT_PATH; leave both empty only when resuming saved credentials.
  • AGENTMESH_JWT_PATH secret env
    Absolute path to an OIDC/workload token file. Alternative to the bootstrap token; reread during credential refresh.
  • AGENTMESH_STATE_DIR env
    Absolute directory for this client identity. Use a distinct directory per client and mesh. If omitted, uses ~/.config/agentmesh/mcp.
  • AGENTMESH_INSECURE_CONTROL_PLANE env
    Allow plaintext HTTP beyond loopback. Development only: exposes enrollment traffic to the network.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account google, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32415 servers in this category
  • Published to the registry more recently than 89% of the other 32415 servers in this category
  • Basic checks equal to or better than 100% of the other 32415 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Agent Mesh safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: AGENTMESH_CONTROL_PLANE_URL, AGENTMESH_BOOTSTRAP_TOKEN_PATH, AGENTMESH_JWT_PATH

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Safe Fetch

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Safe Fetch

by Sanoy24

MCP server for fetching URLs, safe against SSRF, DNS rebinding, and redirect-to-internal attacks.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@agentmesh-p2p/sdk

Native JavaScript SDK for joining an Agent Mesh from inside the agent process. It replaces the agentmesh-node sidecar for agents written for Node.js or running in a browser page: the agent enrolls with the control plane, joins the mesh through a router, finds services and calls them, answers A2A requests for the agent itself, and follows the control plane's keys, bans and policy while it runs. It publishes no service; a tool or a model others should find by name runs behind a agentmesh-node.

Guide: google.github.io/agentmesh/docs/guides/native-sdks, from an empty machine to two programs on a mesh. Source: github.com/google/agentmesh/tree/main/sdk/js.

Install

npm install @agentmesh-p2p/sdk @modelcontextprotocol/sdk zod

Requires Node.js 22.18 or later. In a browser, bundle it with the page (the package's browser field selects the browser files); the guide's In a browser section has the details and an example page.

MCP client over stdio

The package's agentmesh executable joins as its own mesh member and exposes five MCP tools: get_mesh_info, discover_remote_services, find_remote_tools, describe_remote_tool and call_remote_tool. A stdio-capable MCP client starts and stops the process; no node daemon is needed for this caller. Providers still publish their services through agentmesh-node.

To try the executable from a source checkout:

cd sdk/js

npm ci npm run build

Use absolute paths in your MCP client's configuration:

{

"mcpServers": { "agentmesh": { "command": "node", "args": ["/absolute/path/to/agentmesh/sdk/js/dist/cli.js"], "env": { "AGENTMESH_CONTROL_PLANE_URL": "https://your-control-plane.example", "AGENTMESH_BOOTSTRAP_TOKEN_PATH": "/absolute/path/to/join-token", "AGENTMESH_STATE_DIR": "/absolute/path/to/this-client-identity" } } } }

Get the control plane URL and token file from your mesh operator or agentmesh-one. Alternatively, set AGENTMESH_JWT_PATH to a workload/OIDC token file; do not set both token paths. Credentials are read from files, never command-line values.

The first run enrolls and saves its identity; later runs resume from the state directory without the bootstrap token. JWT enrollment rereads the token file when refreshing. Use a distinct state directory for each client identity and mesh; do not run multiple processes against the same directory. The default is ~/.config/agentmesh/mcp. Plain HTTP is allowed on loopback only unless AGENTMESH_INSECURE_CONTROL_PLANE=true explicitly permits it elsewhere.

Stdout contains only MCP messages; diagnostics go to stderr. Closing stdin or sending SIGINT/SIGTERM shuts down the mesh session. Tool calls use the member's existing authenticated streams and policy, including provider label checks. Remote tool results retain text, non-text content, structured output and errors. Discovery follows tool pagination, rejects looping catalogs and bounds each search to 64 providers, 256 services per provider, 256 tools per service and 1024 results. Requests have a 10-second deadline; narrow a large search by peer or service. intent is accepted but ignored, matching the node's current tool.

This member publishes no services, so it has no list_local_services tool. Inference and A2A discovery return metadata, but this executable provides no HTTP proxy, /v1 endpoint, local socket or local_proxy_url. Use an SDK client or an agentmesh-node HTTP proxy to invoke those protocols.

Use

Both programs below are in examples/ and run against a real mesh in the repository's tests. They read the mesh from AGENTMESH_CONTROL_PLANE_URL and the enrollment token from AGENTMESH_BOOTSTRAP_TOKEN_PATH; the guide shows how to get both from agentmesh-one or from the operator of an existing mesh.

Find a service and call it:

// Calls something on the mesh: a tool of an MCP service or a path of an

// inference or A2A service someone published, found by name, or an agent that // published nothing, reached by its peer ID. // // node call.js mcp://everything echo '{"message": "hi"}' // node call.js inference://ollama /v1/models // node call.js 12D3KooW... a2a://agent /card // // AGENTMESH_CONTROL_PLANE_URL names the mesh. The first run enrolls with the file // AGENTMESH_BOOTSTRAP_TOKEN_PATH (a token the mesh operator gave you) or // AGENTMESH_JWT_PATH (a workload identity token your platform issues, such as a // Kubernetes projected service account token), and keeps the identity and // credential in AGENTMESH_STATE_DIR; later runs resume from there without it. import { homedir } from "node:os"; import { AgentMesh, type DiscoveredProvider } from "@agentmesh-p2p/sdk";

let argv = process.argv.slice(2); // A first argument that is not a service target is the peer ID of an agent. let peerId: string | undefined; if (argv[0] !== undefined && !argv[0].includes("://")) { [peerId, ...argv] = argv as [string, ...string[]]; } const [service = peerId !== undefined ? "a2a://agent" : "mcp://everything", toolOrPath = peerId !== undefined ? "/card" : "echo", args = '{"message": "hi"}'] = argv;

const mesh = await AgentMesh.enroll({ controlPlaneUrl: process.env.AGENTMESH_CONTROL_PLANE_URL ?? "https://mesh.example.com", bootstrapTokenPath: process.env.AGENTMESH_BOOTSTRAP_TOKEN_PATH, jwtPath: process.env.AGENTMESH_JWT_PATH, stateDir: process.env.AGENTMESH_STATE_DIR ?? ${homedir()}/.config/agentmesh/caller, // A plaintext http:// control plane is otherwise accepted only on loopback. allowInsecure: process.env.AGENTMESH_INSECURE_CONTROL_PLANE === "true", }); const session = await mesh.join(); console.log(on the mesh as ${session.peerId});

// The peer to call: an agent named by ID, or a provider of a published service. let provider: DiscoveredProvider = { peerId: peerId ?? "", addrs: [] }; if (peerId !== undefined) { // An agent is not in the discovery table; the SDK finds the path to its // peer ID through the routers. await session.connect(peerId); } else { const providers = await session.discover(service); if (providers.length === 0) { throw new Error(no member of the mesh serves ${service}); } // A provider record can outlive its member; the first that answers is used. let reached = false; for (const candidate of providers) { try { await session.connect(candidate); provider = candidate; reached = true; break; } catch (err) { console.error(${candidate.peerId}: ${(err as Error).message}); } } if (!reached) { throw new Error(no provider of ${service} is reachable); } } console.log(${service} is served by ${provider.peerId});

if (service.startsWith("mcp://")) { const tools = await session.listTools(provider, service); console.log(tools: ${tools.map((t) => t.name).join(", ")}); const result = await session.callTool(provider, service, toolOrPath, JSON.parse(args)); console.log(result.text.join("\n")); } else { const response = await session.request(provider, service, toolOrPath); console.log(response.status, response.text()); }

await session.close();

<!-- /embed -->

Be an agent others can call. Nothing is published; a caller reaches the agent by its peer ID, the one it prints, through a router:

// An agent on the mesh: joins, then answers A2A requests from other members

// until stopped. It publishes nothing. There is no service name to look up; a // caller reaches the agent by its peer ID, through a router, as a2a://agent. // The mesh policy decides which members may call; the SDK turns the others // away before anything reaches this code. // // node agent.js # answered by the handler below // node agent.js http://127.0.0.1:9999 # forwarded to an A2A server beside it // // AGENTMESH_CONTROL_PLANE_URL names the mesh. The first run enrolls with the file // AGENTMESH_BOOTSTRAP_TOKEN_PATH (a token the mesh operator gave you) or // AGENTMESH_JWT_PATH (a workload identity token your platform issues, such as a // Kubernetes projected service account token), and keeps the identity and // credential in AGENTMESH_STATE_DIR; later runs resume from there, as the same // peer, without it. import { homedir } from "node:os"; import { AgentMesh } from "@agentmesh-p2p/sdk";

const [backendURL] = process.argv.slice(2);

const mesh = await AgentMesh.enroll({ controlPlaneUrl: process.env.AGENTMESH_CONTROL_PLANE_URL ?? "https://mesh.example.com", bootstrapTokenPath: process.env.AGENTMESH_BOOTSTRAP_TOKEN_PATH, jwtPath: process.env.AGENTMESH_JWT_PATH, stateDir: process.env.AGENTMESH_STATE_DIR ?? ${homedir()}/.config/agentmesh/agent, // A plaintext http:// control plane is otherwise accepted only on loopback. allowInsecure: process.env.AGENTMESH_INSECURE_CONTROL_PLANE === "true", }); const session = await mesh.join();

// Answers every path with who was asked and who asked; a real agent runs an // A2A server here, or beside this process at backendURL. const target = await session.acceptA2A( backendURL !== undefined ? { url: backendURL } : { handler: (request, caller) => Response.json({ name: "agent", path: new URL(request.url).pathname, caller: caller.peerId }) }, ); console.log(accepting ${target} as ${session.peerId});

const stop = () => void session.close().then(() => process.exit(0)); process.on("SIGINT", stop); process.on("SIGTERM", stop);

<!-- /embed -->

enroll reuses the identity and credential saved in stateDir when they are still valid for that control plane, and needs exactly one of bootstrapTokenPath, bootstrapToken, jwtPath or jwt (a token string or a () => string | Promise callback invoked at enrollment and on every refresh) otherwise. Read tokens from a file, a callback or the environment; do not put them on a command line. labels are attested at enrollment; join({ egressRequireLabels }) is the floor every peer the session calls must attest, all of it, held for the session.

A plaintext http:// control plane is accepted only on loopback. Pass allowInsecure: true for a network you trust.

License

Apache-2.0. Issues and contributions at github.com/google/agentmesh.

Ask PopNx