
Agent Mesh
io.github.googlePublished by GitHub account googlev0.2.0Updated Nov 3, 2026
Discover and call remote MCP tools as your own authenticated Agent Mesh member.
The publisher's own server: AgentMesh
Overview
Agent Mesh's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Agent Mesh in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@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
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:
Use absolute paths in your MCP client's configuration:
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:
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:
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.
Source: sdk/js/README.md at commit 1c88bcf
Tools
0Version history
1- v0.2.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts