Crate crabtalk_mcp 

MCP (Model Context Protocol) client, bridge, and dispatcher.

Three layers:

• client — minimal JSON-RPC 2.0 client over stdio or HTTP
• bridge — fleet of connected peers, tool cache, call routing
• handler / dispatch — config-driven load, port-file discovery, meta-tool dispatch

Features

Pick exactly one HTTP backend and one TLS backend:

• hyper (default) / reqwest
• native-tls (default) / rustls

The hyper backend is more compact — it skips reqwest’s cookie store, redirect logic, and decoders that MCP never uses.

Re-exports

pub use bridge::McpBridge;

pub use handler::Fingerprint;

pub use handler::McpEvent;

pub use handler::McpHandler;

pub use handler::McpServerState;

pub use handler::ServerStatus;

pub use handler::fingerprint;

Modules

bridge

Crabtalk MCP bridge — connects to MCP servers and routes tool calls.

client

Minimal MCP client — JSON-RPC 2.0 over stdio or HTTP.

dispatch

MCP tool dispatch — the mcp meta-tool handler.

handler

Crabtalk MCP handler — agent-driven registration with fingerprint-keyed dedup.