Memungkinkan AI agent untuk menemukan dan memanggil remote MCP tools serta layanan melalui authenticated peer-to-peer mesh.
Juga dikenal sebagai google/agentmesh, agentmesh, @agentmesh-p2p/sdk
- Stars
- 1.198
- Tools
- —
- Unduhan, 30 hari
- 798
- Versi terbaru
- 0.2.0
- Commit terakhir
- 13 Nov 2026
- Lisensi
- Apache-2.0
Apa itu Agent Mesh MCP?
Agent Mesh adalah MCP server. Memungkinkan AI agent untuk menemukan dan memanggil remote MCP tools serta layanan melalui authenticated peer-to-peer mesh.
Ringkasan dibuat dari README proyek
Tentang Agent Mesh MCP server
Agent Mesh menyediakan native JavaScript SDK yang memungkinkan AI agent untuk bergabung ke dalam authenticated peer-to-peer mesh. Sistem ini memungkinkan agent untuk menemukan dan berinteraksi dengan remote services, tools, dan agent lainnya tanpa memerlukan local sidecar daemon. Ini dirancang untuk developer yang membangun aplikasi Node.js atau browser-based agents yang perlu berkomunikasi di seluruh distributed network menggunakan control plane untuk manajemen identitas dan kebijakan.
User dapat terhubung ke mesh dengan menyediakan URL control plane dan salah satu dari bootstrap token path atau JWT path. SDK ini mengelola identitas dan kredensial di dalam direktori state yang ditentukan, sehingga sesi berikutnya dapat dilanjutkan tanpa perlu re-enrollment. Bagi Anda yang menggunakan MCP clients standar, executable yang disediakan mengekspos lima tools spesifik: get_mesh_info, discover_remote_services, find_remote_tools, describe_remote_tool, dan call_remote_tool. Setup ini memungkinkan client untuk menemukan dan mengeksekusi remote functions sambil tetap mematuhi aturan ban dan kebijakan keamanan di seluruh mesh.
Apa yang bisa Anda lakukan dengannya
- 1Discover remote MCP toolsAI client dapat mencari di dalam mesh untuk menemukan tools spesifik yang disediakan oleh anggota lainnya.
- 2Execute remote service functionsDeveloper dapat menginstruksikan agent untuk memanggil tool tertentu yang terletak pada remote service melalui mesh.
- 3Enable agent-to-agent communicationAgent dapat merespons permintaan dari peer lainnya menggunakan protokol A2A.
- 4Integrate with existing MCP clientsAnda dapat menggunakan executable agentmesh sebagai MCP server standar melalui stdio.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Agent Mesh MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Agent Mesh MCP di Claude Code
$ 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/sdkInstal Agent Mesh MCP di Cursor
~/.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>"
}
}
}
}Instal Agent Mesh MCP di VS Code
.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>"
}
}
}
}Instal Agent Mesh MCP di VS Code CLI
$ code --add-mcp '{"name":"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>"}}'Instal Agent Mesh MCP di Claude Desktop
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>"
}
}
}
}Instal Agent Mesh MCP di Codex
$ codex mcp add agentmesh --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>' -- npx -y @agentmesh-p2p/sdkInstal Agent Mesh MCP di Codex config.toml
~/.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>"
Instal Agent Mesh MCP di Gemini CLI
$ gemini mcp add -s user -e 'AGENTMESH_CONTROL_PLANE_URL=<AGENTMESH_CONTROL_PLANE_URL>' -e 'AGENTMESH_BOOTSTRAP_TOKEN_PATH=<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>' -e 'AGENTMESH_JWT_PATH=<YOUR_AGENTMESH_JWT_PATH>' agentmesh npx -- -y @agentmesh-p2p/sdkInstal Agent Mesh MCP di Gemini settings.json
~/.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>"
}
}
}
}Konfigurasi
AGENTMESH_CONTROL_PLANE_URLWajibControl plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below.
AGENTMESH_BOOTSTRAP_TOKEN_PATHRahasiaAbsolute 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_PATHRahasiaAbsolute 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.
| Nama | Deskripsi | Tipe |
|---|---|---|
| AGENTMESH_CONTROL_PLANE_URL | Control plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below. | Wajib |
| 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. | Rahasia |
| AGENTMESH_JWT_PATH | Absolute path to an OIDC/workload token file. Alternative to the bootstrap token; reread during credential refresh. | Rahasia |
| 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. |
Pengecekan otomatis
Berjalan 12 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSTidak diperiksa
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaLolos
README
Lihat di GitHub@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.
Pertanyaan tentang Agent Mesh MCP
Bagaimana cara menambahkan Agent Mesh MCP ke Claude Code?
Jalankan 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 di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Agent Mesh MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bagaimana cara menggunakan Agent Mesh dengan MCP client?
Anda dapat menggunakan executable agentmesh yang bergabung sebagai anggota mesh dan mengekspos lima MCP tools: get_mesh_info, discover_remote_services, find_remote_tools, describe_remote_tool, dan call_remote_tool.
Apakah executable Agent Mesh mempublikasikan layanan lokal?
Tidak, executable ini tidak mempublikasikan layanan apa pun; ia dirancang untuk menemukan dan memanggil remote tools. Untuk mempublikasikan layanan, Anda harus menggunakan agentmesh-node.
Bisakah saya menggunakan plain HTTP control plane?
Plain HTTP hanya diizinkan pada loopback address kecuali jika Anda mengaktifkannya secara eksplisit menggunakan environment variable AGENTMESH_INSECURE_CONTROL_PLANE=true.