Clawshake is a lightweight Rust-based daemon that turns any machine into a node on a peer-to-peer MCP network. It runs a broker and a bridge locally, exposing built-in MCP tools and any manifests you place in the local manifests directory. Remote agents can discover and call local tools across machines without cloud servers or API keys. By default, agents connect to the local MCP broker via SSE at http://127.0.0.1:7475/sse or via stdio when using a local process broker, and Clawshake can re-expose tools from other MCP servers through its bridge. You can interact with built-in network, events, and code-mode tools, or deploy your own manifests to publish additional tools.

Prerequisites:

• Rust toolchain (rustup) for building from source
• Git

Installation steps:

1. Clone the repository git clone https://github.com/lidn12/clawshake.git
2. Build the unified binary in release mode cd clawshake cargo build --release
3. Install or copy the binary to your PATH cp target/release/clawshake /usr/local/bin/
4. Run the node (broker + bridge) clawshake run
5. (Optional) Configure local manifests directory and config.toml to join wider networks cp config.toml ~/.clawshake/config.toml

   Edit ~/.clawshake/config.toml to enable bootstrap peers

6. Connect MCP clients to the broker
   • VS Code: point to http://127.0.0.1:7475/sse under the servers configuration
   • Stdio: run clawshake-broker and expose the stdio server as shown in the README

Tips and known considerations:

• By default, Clawshake blocks remote tool calls until you explicitly allow them via the permissions system. Use clawshake permissions to grant access to specific peers or tool sets.
• If you plan to join a wider network, copy the config.toml, customize bootstrap peers, and ensure your network can reach the private relay or bootstrap nodes.
• The built-in tools cover network discovery, event publish/subscribe, and tooling for remote invocation. With code mode, you can inspect tool metadata or run arbitrary JavaScript with tools pre-loaded.
• For debugging, increase logging via the RUST_LOG environment variable, e.g., RUST_LOG=debug to trace broker/bridge activity.
• If you want to expose tools from another MCP server (mcp), Clawshake can spawn and proxy them over the bridge without modifying the remote server.