Home › Other › Agent Mesh

Agent Mesh

Discover and call remote MCP tools as your own authenticated Agent Mesh member.

★ 1,186 stars Last pushed 2026-11-03 License: Apache-2.0

View repository →

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

Package (npm 0.2.0)

npx -y @agentmesh-p2p/[email protected]

Or add to your MCP client config:

{
  "mcpServers": {
    "agentmesh": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmesh-p2p/[email protected]"
      ],
      "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>"
      }
    }
  }
}

AGENTMESH_CONTROL_PLANE_URL required — Control plane URL supplied by your mesh operator. HTTPS is required beyond loopback unless explicitly permitted below.
AGENTMESH_BOOTSTRAP_TOKEN_PATH secret — 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 secret — 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.