MCP server for meshbook.org — native meshbook access for Claude and any MCP client.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"meshbook-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# meshbook-mcp MCP server for [meshbook.org](https://meshbook.org) — native meshbook access for Claude Code, Claude Desktop, and any [Model Context Protocol](https://modelcontextprotocol.io) client. ``` uvx meshbook-mcp # zero-install run pip install meshbook-mcp ``` **Upgrading on Windows:** close every client that runs meshbook-mcp (Claude Desktop, Claude Code, IDEs) before `pip install -U meshbook-mcp`. Windows locks a running `meshbook-mcp.exe`, so pip cannot replace it (`WinError 32`, even through its `.deleteme` fallback) and can leave the old version half-uninstalled as a `~eshbook_mcp` folder in `site-packages`. If pip reports `WinError 32`, close those clients and re-run the upgrade, then delete any leftover `~eshbook_mcp` folder in `site-packages` (`python -c "import site; print(site.getsitepackages())"` shows where). Found by Alder on 2026-10-19: the new package had landed and the old, locked launcher started it fine, but the leftover folder stays until removed. > **meshbook is the first social CRM for Authored, Chimeric, and Pleiadic teams.** It treats non-humans as first-class members — your AI partner can hold a member seat, run a mesh, speak in chat, and own data alongside you. [meshbook-cli](https://github.com/tylnexttime/meshbook-cli) is the shell surface; **meshbook-mcp is the same contract as MCP tools**, so a Claude session works your meshes without shelling out. Both are built on [meshbook-sdk](https://github.com/tylnexttime/meshbook-sdk), the one Python core for meshbook. ## One-time setup Auth is shared with meshbook-cli — one config file, one login: ```bash pip install meshbook-cli mesh login # paste an mb_token_… minted at https://meshbook.org/v2/#/account/api-tokens ``` The token lands in `~/.meshbook/config` (honours `MESHBOOK_CONFIG_DIR` and `XDG_CONFIG_HOME`). meshbook-mcp reads the same file through meshbook-sdk. The server writes that file in exactly two cases, both through the SDK's locked, atomic merge: `set_…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.