Ermöglicht es AI Agents, remote MCP Tools und Services über ein authentifiziertes Peer-to-Peer Mesh zu entdecken und aufzurufen.
Auch bekannt als google/agentmesh, agentmesh, @agentmesh-p2p/sdk
- Stars
- 1.198
- Tools
- —
- Downloads, 30 Tage
- 798
- Neueste Version
- 0.2.0
- Letzter Commit
- 13. Nov. 2026
- Lizenz
- Apache-2.0
Was ist Agent Mesh MCP?
Agent Mesh ist ein MCP server. Ermöglicht es AI Agents, remote MCP Tools und Services über ein authentifiziertes Peer-to-Peer Mesh zu entdecken und aufzurufen.
Zusammenfassung generiert aus dem README des Projekts
Über Agent Mesh MCP server
Agent Mesh bietet ein natives JavaScript SDK, mit dem AI Agents einem authentifizierten Peer-to-Peer Mesh beitreten können. Dieses System ermöglicht es Agents, remote Services, Tools und andere Agents zu entdecken und mit ihnen zu interagieren, ohne dass ein lokaler Sidecar-Daemon erforderlich ist. Es wurde für Entwickler konzipiert, die Node.js-Anwendungen oder browserbasierte Agents bauen, die über ein verteiltes Netzwerk kommunizieren müssen, wobei ein Control Plane für das Identity- und Policy-Management genutzt wird.
Nutzer können sich mit dem Mesh verbinden, indem sie eine Control Plane URL sowie entweder einen Pfad zu einem Bootstrap Token oder zu einem JWT angeben. Das SDK verwaltet Identitäten und Credentials innerhalb eines festgelegten State-Verzeichnisses, sodass nachfolgende Durchläufe Sessions ohne erneute Registrierung fortsetzen können. Für diejenigen, die Standard-MCP Clients nutzen, stellt das bereitgestellte Executable fünf spezifische Tools bereit: get_mesh_info, discover_remote_services, find_remote_tools, describe_remote_tool und call_remote_tool. Dieses Setup erlaubt es einem Client, remote Funktionen zu finden und auszuführen, während gleichzeitig meshweite Verbote und Security-Policies eingehalten werden.
Was du damit machen kannst
- 1Remote MCP Tools entdeckenEin AI Client kann das Mesh durchsuchen, um spezifische Tools zu finden, die von anderen Mitgliedern bereitgestellt werden.
- 2Remote Service Funktionen ausführenEin Entwickler kann einen Agent anweisen, ein spezifisches Tool aufzurufen, das über das Mesh auf einem remote Service liegt.
- 3Agent-to-Agent Kommunikation ermöglichenAgents können auf Anfragen von anderen Peers über das A2A-Protokoll antworten.
- 4Integration in bestehende MCP ClientsDu kannst das agentmesh Executable als Standard-MCP Server via stdio nutzen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Agent Mesh MCP
Formate geprüft am 10. Nov. 2026Agent Mesh MCP in Claude Code installieren
$ claude mcp add --env AGENTMESH_CONTROL_PLANE_URL=<AGENTMESH_CONTROL_PLANE_URL> --env AGENTMESH_BOOTSTRAP_TOKEN_PATH=<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH> --env AGENTMESH_JWT_PATH=<YOUR_AGENTMESH_JWT_PATH> agentmesh -- npx -y @agentmesh-p2p/sdkAgent Mesh MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"agentmesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>",
"AGENTMESH_JWT_PATH": "<YOUR_AGENTMESH_JWT_PATH>"
}
}
}
}Agent Mesh MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"agentmesh": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>",
"AGENTMESH_JWT_PATH": "<YOUR_AGENTMESH_JWT_PATH>"
}
}
}
}Agent Mesh MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"agentmesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>",
"AGENTMESH_JWT_PATH": "<YOUR_AGENTMESH_JWT_PATH>"
}
}
}
}Agent Mesh MCP in Codex installieren
~/.codex/config.toml
[mcp_servers.agentmesh] command = "npx" args = ["-y", "@agentmesh-p2p/sdk"] [mcp_servers.agentmesh.env] AGENTMESH_CONTROL_PLANE_URL = "<AGENTMESH_CONTROL_PLANE_URL>" AGENTMESH_BOOTSTRAP_TOKEN_PATH = "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>" AGENTMESH_JWT_PATH = "<YOUR_AGENTMESH_JWT_PATH>"
Agent Mesh MCP in Gemini CLI installieren
~/.gemini/settings.json
{
"mcpServers": {
"agentmesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>",
"AGENTMESH_JWT_PATH": "<YOUR_AGENTMESH_JWT_PATH>"
}
}
}
}Konfiguration
AGENTMESH_CONTROL_PLANE_URLErforderlichControl plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below.
AGENTMESH_BOOTSTRAP_TOKEN_PATHSecretAbsolute 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_PATHSecretAbsolute path to an OIDC/workload token file. Alternative to the bootstrap token; reread during credential refresh.
AGENTMESH_INSECURE_CONTROL_PLANEAllow plaintext HTTP beyond loopback. Development only: exposes enrollment traffic to the network.
AGENTMESH_STATE_DIRAbsolute directory for this client identity. Use a distinct directory per client and mesh. If omitted, uses ~/.config/agentmesh/mcp.
| Name | Beschreibung | Typ |
|---|---|---|
| AGENTMESH_CONTROL_PLANE_URL | Control plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below. | Erforderlich |
| AGENTMESH_BOOTSTRAP_TOKEN_PATH | Absolute path to a bootstrap token file for first enrollment. Set this OR AGENTMESH_JWT_PATH; leave both empty only when resuming saved credentials. | Secret |
| AGENTMESH_JWT_PATH | Absolute path to an OIDC/workload token file. Alternative to the bootstrap token; reread during credential refresh. | Secret |
| AGENTMESH_INSECURE_CONTROL_PLANE | Allow plaintext HTTP beyond loopback. Development only: exposes enrollment traffic to the network. | |
| AGENTMESH_STATE_DIR | Absolute directory for this client identity. Use a distinct directory per client and mesh. If omitted, uses ~/.config/agentmesh/mcp. |
Automatisierte Checks
Geluften am 12. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertNicht geprüft
- Keine versteckten Anweisungen an das ModellBestanden
- Kein kritischer Hinweis im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehen@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();
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);
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<string> 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.
Agent Mesh MCP Fragen
Wie füge ich Agent Mesh MCP zu Claude Code hinzu?
Führe claude mcp add --env AGENTMESH_CONTROL_PLANE_URL=<AGENTMESH_CONTROL_PLANE_URL> --env AGENTMESH_BOOTSTRAP_TOKEN_PATH=<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH> --env AGENTMESH_JWT_PATH=<YOUR_AGENTMESH_JWT_PATH> agentmesh -- npx -y @agentmesh-p2p/sdk in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Agent Mesh MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wie kann ich Agent Mesh mit einem MCP Client nutzen?
Du kannst das agentmesh Executable verwenden, das sich als Mesh-Mitglied anmeldet und fünf MCP Tools bereitstellt: get_mesh_info, discover_remote_services, find_remote_tools, describe_remote_tool und call_remote_tool.
Veröffentlicht das Agent Mesh Executable lokale Services?
Nein, das Executable veröffentlicht keine Services; es ist darauf ausgelegt, remote Tools zu entdecken und aufzurufen. Um Services zu veröffentlichen, solltest du agentmesh-node verwenden.
Kann ich ein einfaches HTTP Control Plane nutzen?
Einfaches HTTP ist nur auf der Loopback-Adresse erlaubt, es sei denn, du aktivierst es explizit über die Umgebungsvariable AGENTMESH_INSECURE_CONTROL_PLANE=true.