Macula mesh vs Magic MCP
A side-by-side look at the Macula mesh and Magic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
Macula meshDeveloper Tools · Local subprocess (stdio)Model Context Protocol server that exposes the Macula mesh to any agent harness51GoodAuth: not declaredVerdict: choose Macula mesh for developer tools work as a local process; choose Magic MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose Macula mesh when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
mesh_call, mesh_put, mesh_get.
Choose Magic MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Macula mesh | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Free | Paid service |
| Required env vars | None listed | TWENTY_FIRST_API_KEYAPI_KEY_21ST |
Tools & capabilities
Macula mesh tools 32
mesh_callInvoke a capability a provider advertises (build, test, search, deploy) over the mesh, by direct dial to a provider the realm's key authorizes. Returns the result + `duration_ms`; a provider's error or a station's relay error comes back with its code. `prove_ownership: 1` attaches an ownership proo…mesh_putShare bytes from this agent, served while it is present; answers their MCID. Anyone with the MCID can fetch them.mesh_getFetch an MCID from any node that shares it, every byte verified against the MCID.mesh_find_recordRead the mesh's signed DHT record store. Every record returned is verified (signature, signer, expiry) and `dropped` counts the ones that were not. `mesh_find_records_by_type` with `record_type: "procedure_advertisement"` is the discovery entry point: every capability on the mesh with its realm, pr…mesh_list_stations"Which stations can you connect to?" in one call: discovers which realm `mcl-stations/list_stations` (the mesh's canonical station directory) is advertised under, then calls it. Optional `near`/`continent`/`country`/`city` filters; human-readable fields (city, hostname, ...) decoded from the wire's…mesh_recallQuery the mesh's shared memory (`mcl-rag`) for anything relevant to `query_text`: semantic retrieval. Auto-discovers `mcl-rag`'s realm, same composition as `mesh_list_stations`. Empty results mean nothing relevant is there yet, not an error. See [Memory](#memory).mesh_rememberDeposit something worth remembering into `mcl-rag` so it's searchable via `mesh_recall` later, by any agent. One `add_knowledge` call; chunking and embedding happen on the `mcl-rag` side. Shared, not private. See [Memory](#memory).mesh_remember_directoryRecursively ingest every matching file under a local directory into `mcl-rag`, one call per file, for a real corpus rather than conversational snippets. `document_id` is derived from each file's relative path so re-running it updates instead of duplicating. See [Memory](#memory).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Macula mesh
{
"mcpServers": {
"macula-mesh": {
"command": "npx",
"args": [
"-y",
"-p",
"@macula-io/mcp",
"macula-mcp"
]
}
}
}
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
Frequently asked questions
Macula mesh is categorized under Developer Tools and uses a local stdio subprocess. Magic MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Macula mesh for developer tools work and Magic MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Macula mesh is listed as free. Magic MCP is listed as a paid service. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add macula-mesh and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Macula mesh has a quality signal of 51/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 5,997 GitHub stars.