Agent Mesh
MCP server by Google
Discover and call MCP tools published by other nodes on a private, identity-verified network of AI agents.
Install Agent Mesh
Runs on your machine. Your client starts it with this command:
Needs Node.js on your computer. The setup steps below show where the command goes in each client.
AGENTMESH_CONTROL_PLANE_URLControl plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below.AGENTMESH_BOOTSTRAP_TOKEN_PATHsecret optional Absolute path to a bootstrap token file for first enrollment. Set this OR AGENTMESH_JWT_PATH; leave both empty only when resuming saved…AGENTMESH_JWT_PATHsecret optional Absolute path to an OIDC/workload token file. Alternative to the bootstrap token; reread during credential refresh.AGENTMESH_STATE_DIRoptional Absolute directory for this client identity. Use a distinct directory per client and mesh. If omitted, uses ~/.config/agentmesh/mcp.AGENTMESH_INSECURE_CONTROL_PLANEoptional Allow plaintext HTTP beyond loopback. Development only: exposes enrollment traffic to the network.
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/agent-meshAbout
Agent Mesh is a private network for AI agents. This package runs a local MCP client that enrolls as a member of a mesh, then lets an agent discover and call tools that other nodes publish. Nothing is reachable by default, and calls are checked against the mesh policy by service name.
It runs locally over stdio through npx (@agentmesh-p2p/sdk). It needs a control plane URL from your mesh operator, plus either a bootstrap token file for first enrollment or an OIDC/workload token file. The project states it is not an officially supported Google product.
What you can do
- Enroll as an authenticated member of an Agent Mesh
- Discover tools and services published by other mesh nodes
- Call remote MCP tools across the mesh
- Use OIDC or bootstrap tokens for identity
- Resume saved credentials from a state directory
Tools
Agent Mesh lists its tools only to clients with a key, so we can’t show them here.
Example prompts
Find which tools are published on my mesh.
Call the remote search tool on the mesh and show me the result.
List the services my node is allowed to call.
Enroll this client into my mesh using the bootstrap token.
Set up
Every client starts Agent Mesh on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio agent-mesh --env "AGENTMESH_CONTROL_PLANE_URL=<YOUR_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/sdk- Start Claude Code and type
/mcp. agent-mesh should show as connected.
Add --scope user to make it available in every project. Replace the placeholders with your own values.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"agent-mesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<YOUR_AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>",
"AGENTMESH_JWT_PATH": "<YOUR_AGENTMESH_JWT_PATH>"
}
}
}
}- Save the file and restart Claude Desktop. Replace the placeholders with your own values.
Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"agent-mesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<YOUR_AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>",
"AGENTMESH_JWT_PATH": "<YOUR_AGENTMESH_JWT_PATH>"
}
}
}
}Needs Node.js on your computer. Replace the placeholders with your own values.
VS Code
Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:
{
"servers": {
"agent-mesh": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<YOUR_AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "${input:agentmesh-bootstrap-token-path}",
"AGENTMESH_JWT_PATH": "${input:agentmesh-jwt-path}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "agentmesh-bootstrap-token-path",
"description": "AGENTMESH_BOOTSTRAP_TOKEN_PATH",
"password": true
},
{
"type": "promptString",
"id": "agentmesh-jwt-path",
"description": "AGENTMESH_JWT_PATH",
"password": true
}
]
}Needs Node.js on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"agent-mesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<YOUR_AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>",
"AGENTMESH_JWT_PATH": "<YOUR_AGENTMESH_JWT_PATH>"
}
}
}
}- Refresh the MCP server list in Cascade. Replace the placeholders with your own values.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add agent-mesh --env "AGENTMESH_CONTROL_PLANE_URL=<YOUR_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/sdkOr edit ~/.codex/config.toml directly:
[mcp_servers.agent-mesh]
command = "npx"
args = ["-y", "@agentmesh-p2p/sdk"]
env = { AGENTMESH_CONTROL_PLANE_URL = "<YOUR_AGENTMESH_CONTROL_PLANE_URL>", AGENTMESH_BOOTSTRAP_TOKEN_PATH = "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>", AGENTMESH_JWT_PATH = "<YOUR_AGENTMESH_JWT_PATH>" }Needs Node.js on your computer. Replace the placeholders with your own values.
Gemini CLI
gemini mcp add -e "AGENTMESH_CONTROL_PLANE_URL=<YOUR_AGENTMESH_CONTROL_PLANE_URL>" -e "AGENTMESH_BOOTSTRAP_TOKEN_PATH=<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>" -e "AGENTMESH_JWT_PATH=<YOUR_AGENTMESH_JWT_PATH>" agent-mesh npx -- -y @agentmesh-p2p/sdkThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"agent-mesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<YOUR_AGENTMESH_CONTROL_PLANE_URL>",
"AGENTMESH_BOOTSTRAP_TOKEN_PATH": "<YOUR_AGENTMESH_BOOTSTRAP_TOKEN_PATH>",
"AGENTMESH_JWT_PATH": "<YOUR_AGENTMESH_JWT_PATH>"
}
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs Node.js on your computer. Replace the placeholders with your own values.
Embed
Show Agent Mesh in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/agent-mesh)<a href="https://mcp.tc/i/agent-mesh"><img src="https://mcp.tc/i/agent-mesh/badge.svg" alt="Agent Mesh on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/agent-mesh.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/agent-mesh" title="Agent Mesh on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/agent-mesh.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Agent Mesh card to your site.
Add the mcp.tc card for Agent Mesh, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/agent-mesh.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="agent-mesh"><a href="https://mcp.tc/i/agent-mesh">Agent Mesh on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/agent-mesh)
```
Reference: https://mcp.tc/embedChange history
This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.
FAQ
Can I paste mcp.tc/i/agent-mesh into my MCP client?
No. Agent Mesh runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @agentmesh-p2p/sdk.
Does Agent Mesh need an API key?
Yes. It reads AGENTMESH_CONTROL_PLANE_URL, AGENTMESH_BOOTSTRAP_TOKEN_PATH and AGENTMESH_JWT_PATH from its environment, and AGENTMESH_BOOTSTRAP_TOKEN_PATH and AGENTMESH_JWT_PATH are secrets. Put the values in your client’s config on your own machine, never in a shared file.
Is Agent Mesh a remote or a local server?
Local. Your client starts it as a process on your computer with npx -y @agentmesh-p2p/sdk, which needs Node.js.
What can Agent Mesh do?
You can enroll as an authenticated member of an Agent Mesh, discover tools and services published by other mesh nodes and call remote MCP tools across the mesh.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Does mcp.tc track changes to Agent Mesh?
Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Agent Mesh’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Google. This page was built from Agent Mesh’s public metadata, last checked on 2 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.