Expand description
§rig-mcp
Model Context Protocol bridge for rig-compose
tool registries, backed by the official rmcp SDK.
Skills cannot tell an McpTool apart from a rig_compose::LocalTool
— both implement the same Tool trait.
The same registry can be exposed as an MCP server via serve_stdio
and consumed by another process via StdioTransport::spawn, with
all spec-level concerns (JSON-RPC framing, capability handshakes,
protocol-version negotiation) delegated to rmcp.
Re-exports§
pub use cache_tools::CACHE_PAGE_TOOL;pub use cache_tools::CACHE_RELEASE_TOOL;pub use cache_tools::CachedResultsConfig;pub use cache_tools::CachedResultsTransport;pub use cache_tools::cache_page_tool;pub use cache_tools::cache_release_tool;pub use cache_tools::cache_tools;pub use cache_tools::register_cache_tools;pub use replay::RegistrationReplayPolicy;pub use replay::RegistrationSnapshot;pub use result_cache::CachedResultEnvelope;pub use result_cache::CachedResultHandle;pub use result_cache::MemoryResultCache;pub use result_cache::ResultCache;pub use result_cache::cache_if_large;pub use stdio::StdioTransport;pub use stdio::serve_stdio;pub use transport::LoopbackTransport;pub use transport::McpTool;pub use transport::McpTransport;
Modules§
- cache_
tools - Model-boundary result-cache integration for MCP transports.
- replay
- Adapter-local registration snapshots for reconnect/replay flows.
- result_
cache - Result-cache layer for large MCP tool outputs.
- stdio
- Stdio MCP transport, backed by the official
rmcpSDK. - transport
- Model Context Protocol transport abstraction.