Agent Mesh runs on your own machine — the client starts it, so there is no endpoint to ping. 11 installs a week from npm. Last commit 2 Nov 2026.
Discover and call remote MCP tools as your own authenticated Agent Mesh member.
Today is the operative word: we check Agent Mesh every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add agentmesh -e 'AGENTMESH_CONTROL_PLANE_URL=<AGENTMESH_CONTROL_PLANE_URL>' -- npx -y @agentmesh-p2p/sdk
{
"mcpServers": {
"agentmesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<AGENTMESH_CONTROL_PLANE_URL>"
}
}
}
}
[mcp_servers.agentmesh]
command = "npx"
args = ["-y", "@agentmesh-p2p/sdk"]
env = { AGENTMESH_CONTROL_PLANE_URL = "<AGENTMESH_CONTROL_PLANE_URL>" }
{
"mcpServers": {
"agentmesh": {
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<AGENTMESH_CONTROL_PLANE_URL>"
}
}
}
}
{
"servers": {
"agentmesh": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agentmesh-p2p/sdk"
],
"env": {
"AGENTMESH_CONTROL_PLANE_URL": "<AGENTMESH_CONTROL_PLANE_URL>"
}
}
}
}
Put your own value in place of
<AGENTMESH_CONTROL_PLANE_URL> (Control plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
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_STATE_DIR (Absolute directory for this client identity. Use a distinct directory per client and mesh. If omitted, uses ~/.config/agentmesh/mcp), AGENTMESH_INSECURE_CONTROL_PLANE (Allow plaintext HTTP beyond loopback. Development only: exposes enrollment traffic to the network).
Google Chat as MCP tools: read, search and write to your spaces, direct messages and sidebar.
One MCP for any agent: your connected apps, shared memory, web search, social data and media tools.
Gmail over MCP from your own account: search, read threads and messages, labels and drafts.
Google Docs as MCP tools: read, edit, suggest and comment on documents.
MCP Toolbox for Databases enables your agent to connect to your database.
MCP Toolbox for Databases enables your agent to connect to your database.
Google Analytics 4 MCP server with reporting, schema discovery, and admin visibility tools
Gmail Postmaster Tools v2 — domains, traffic metrics, and compliance via your own Google OAuth.
Answers built from our own checks of this server.