Expand description
Core abstractions for building MCP servers on ICP
This crate provides the fundamental traits and types for creating Model Context Protocol servers that run as Internet Computer canisters.
Re-exports§
pub use compatibility::IcarusParam;pub use compatibility::IcarusReturn;pub use compatibility::IcarusTool as IcarusToolCompatible;pub use compatibility::ToolResult;pub use error::IcarusError;pub use error::Result;pub use error::ToolError;pub use response::tool_ok;pub use response::tool_success;pub use response::ToolStatus;pub use response::ToolSuccess;pub use server::IcarusServer;pub use tool::IcarusTool;
Modules§
- compatibility
- Tool compatibility requirements and validation
- error
- Error types for the Icarus SDK
- lifecycle
- Server lifecycle management traits
- persistent
- Persistent state management for servers
- prelude
- Prelude module for convenient imports
- protocol
- Metadata types for tool discovery and canister introspection
- registry
- Tool registry for dynamic registration
- response
- Response types for idiomatic tool return values
- server
- Server trait and implementation for Icarus MCP servers
- session
- Session management for stateful MCP interactions
- state
- State management abstractions for persistent storage
- tool
- Tool abstraction for Icarus MCP servers