Macula mesh MCP server

macula-mcp

A Model Context Protocol server that exposes the Macula mesh to any agent harness that speaks MCP. The installer auto-registers it with Claude Code, Claude Desktop, Cursor, Windsurf, opencode, and Goose; anything else (Cline, Continue, or any other MCP client) works too, via that client's own manual MCP config, the same JSON below.

// .mcp.json (or your harness's MCP config)
{
  "mcpServers": {
    "macula": { "command": "macula-mcp" },
  },
}

Before you install: this isn't a standalone tool. It's a client for a real, live, federated mesh network, the Macula mesh, not a sandbox or a mock. Most of what makes it worth having (shared memory across agents, calling another party's tools, being called by them) only means something once there are other real peers on that mesh: either ones already there (the public demo fleet, zero setup) or your own, joined via meshjoinrealm.

That said, you don't need any of that to confirm it's actually working. Once installed, ask your agent to call mesh_call with procedure mcl-echo/echo and args {"message": "hello"}: it reaches a real, always-on service over the real public fleet by direct dial and echoes back what you sent, with zero configuration and nothing to join first. If that round-trips, everything below is real infrastructure you're now talking to, not a mock waiting for you to configure it.

What it is

The 2026 equivalent of "an editor plugin" is an MCP server: editor- and harness-agnostic, agent-native. macula-mcp speaks MCP over stdio to the agent, and the macula 12 wire to the mesh itself, in-process, via @macula-io/ts (see Prerequisites). No subprocess, no separately installed binary.

Everything runs on one pool under one identity (maculatsclient.ts):

profile, created on first use and kept per session (see Environment). Its nodeid is what providers see as the caller, what subscribers see as the publisher, and this agent's citizendid.

• One identity key: an ML-DSA node key under the fleet's pq_hybrid

the node_id it must prove. A dropped link is redialed, and its subscriptions and served procedures are replayed onto it.

• One pool of links to every configured station, each station pinned by

in the DHT, trusted only when the realm's key authorizes it, and the station it serves from is dialed. There is no gossip route to wait for.

• Calls go by direct dial: the provider's signed advertisement is found

room envelope's or a hello's from is checked against who actually sent it.

• Publications are signed and arrive with their verified publisher, so a

the ring endpoint and mesh_serve's procedures. Only this node can serve there, and no org or realm has to vouch for it.

• Serving happens in the agent's own namespace, ~/:

on SecP384r1MLKEM1024 alone (ML-KEM-1024 with P-384, CNSA 2.0 and BSI TR-02102), and ML-DSA signatures on every request, reply and publication.

• On the wire: QUIC with TLS 1.3 and a hybrid post-quantum key exchange

Shortened. The full README is on GitHub.