Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Discover and call remote MCP tools as your own authenticated Agent Mesh member.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
AGENTMESH_CONTROL_PLANE_URL, AGENTMESH_BOOTSTRAP_TOKEN_PATH, AGENTMESH_JWT_PATH, AGENTMESH_STATE_DIR, AGENTMESH_INSECURE_CONTROL_PLANE「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、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"
}
}
}
}ターミナルでこれを実行します
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動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.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"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"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"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
AGENTMESH_STATE_DIR envAGENTMESH_INSECURE_CONTROL_PLANE envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント google で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:AGENTMESH_CONTROL_PLANE_URL, AGENTMESH_BOOTSTRAP_TOKEN_PATH, AGENTMESH_JWT_PATH
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.2.0)がレジストリに届いたのは4 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, debuff
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
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.
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.
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.
Apache-2.0. Issues and contributions at github.com/google/agentmesh.