인증된 P2P mesh를 통해 AI agent가 원격 MCP tool 및 service를 검색하고 호출할 수 있도록 지원합니다.
다른 이름 google/agentmesh, agentmesh, @agentmesh-p2p/sdk
- 스타
- 1,198
- Tools
- —
- 다운로드, 30일
- 798
- 최신 버전
- 0.2.0
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- Apache-2.0
Agent Mesh MCP란?
Agent Mesh은(는) MCP server입니다. 인증된 P2P mesh를 통해 AI agent가 원격 MCP tool 및 service를 검색하고 호출할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
Agent Mesh MCP server 정보
Agent Mesh는 AI agent가 인증된 P2P mesh에 참여할 수 있도록 지원하는 네이티브 JavaScript SDK를 제공합니다. 이 시스템을 통해 agent는 로컬 sidecar daemon 없이도 원격 service, tool 및 other agent를 검색하고 상호작용할 수 있습니다. identity 및 policy 관리를 위한 control plane을 사용하여 분산 네트워크 환경에서 통신이 필요한 Node.js 애플리케이션 또는 브라우저 기반 agent 개발자를 위해 설계되었습니다.
사용자는 control plane URL과 bootstrap token 경로 또는 JWT 경로를 제공하여 mesh에 연결할 수 있습니다. SDK는 지정된 state directory 내에서 identity와 credentials를 관리하므로, 이후 실행 시 재등록 없이 세션을 재개할 수 있습니다. 표준 MCP client를 사용하는 경우, 제공된 실행 파일은 get_mesh_info, discover_remote_services, find_remote_tools, describe_remote_tool, call_remote_tool의 5가지 특정 tool을 노출합니다. 이 설정을 통해 client는 mesh 전체의 ban 및 security policy를 준수하면서 원격 함수를 찾아 실행할 수 있습니다.
활용 사례
- 1원격 MCP tool 검색AI client가 mesh를 검색하여 other member가 제공하는 특정 tool을 찾을 수 있습니다.
- 2원격 service 함수 실행개발자가 agent에게 mesh를 통해 원격 service에 위치한 특정 tool을 호출하도록 지시할 수 있습니다.
- 3agent 간 통신 활성화agent가 A2A protocol을 사용하여 other peer의 요청에 응답할 수 있습니다.
- 4기존 MCP client와 통합agentmesh 실행 파일을 stdio를 통한 표준 MCP server로 사용할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Agent Mesh MCP 설치 방법
형식 확인: 2026년 11월 10일Claude Code에 Agent Mesh MCP 설치
$ 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/sdkCursor에 Agent Mesh MCP 설치
~/.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>"
}
}
}
}VS Code에 Agent Mesh MCP 설치
.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>"
}
}
}
}Claude Desktop에 Agent Mesh MCP 설치
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>"
}
}
}
}Codex에 Agent Mesh MCP 설치
~/.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>"
Gemini CLI에 Agent Mesh MCP 설치
~/.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>"
}
}
}
}구성
AGENTMESH_CONTROL_PLANE_URL필수Control plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below.
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.
AGENTMESH_JWT_PATH비밀Absolute 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.
| 이름 | 설명 | 유형 |
|---|---|---|
| AGENTMESH_CONTROL_PLANE_URL | Control plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below. | 필수 |
| 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. | 비밀 |
| AGENTMESH_JWT_PATH | Absolute path to an OIDC/workload token file. Alternative to the bootstrap token; reread during credential refresh. | 비밀 |
| 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. |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지와 의존성에 심각한 보안 권고 없음통과
README
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.
Agent Mesh MCP 질문
Agent Mesh MCP를 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/sdk를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Agent Mesh MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
MCP client에서 Agent Mesh를 어떻게 사용하나요?
agentmesh 실행 파일을 사용하면 mesh 멤버로 참여하여 get_mesh_info, discover_remote_services, find_remote_tools, describe_remote_tool, call_remote_tool 등 5가지 MCP tool을 사용할 수 있습니다.
Agent Mesh 실행 파일이 로컬 service를 게시하나요?
아니요, 해당 실행 파일은 service를 게시하지 않으며 원격 tool을 검색하고 호출하도록 설계되었습니다. service를 게시하려면 agentmesh-node를 사용해야 합니다.
일반 HTTP control plane을 사용할 수 있나요?
AGENTMESH_INSECURE_CONTROL_PLANE=true 환경 변수를 사용하여 명시적으로 활성화하지 않는 한, 일반 HTTP는 loopback 주소에서만 허용됩니다.