Expand description
Model Context Protocol implementation for OxiFY
Re-exports§
pub use auth::ApiKeyAuth;pub use auth::AuthConfig;pub use auth::AuthMethod;pub use auth::AuthenticatedHttpTransport;pub use auth::BasicAuth;pub use auth::BearerAuth;pub use auth::CredentialStore;pub use auth::CustomHeaderAuth;pub use registry::LoadBalanceConfig;pub use registry::LoadBalanceStrategy;pub use registry::McpRegistry;pub use registry::RegistryStats;pub use registry::ServerEntry;pub use registry::ServerHealth;pub use registry::ServerMetrics;pub use servers::DatabaseConfig;pub use servers::DatabaseServer;pub use servers::DatabaseType;pub use servers::ExecuteResult;pub use servers::FilesystemServer;pub use servers::GitServer;pub use servers::QueryResult;pub use servers::ShellServer;pub use servers::StatementResult;pub use servers::TransactionResult;pub use servers::WebServer;pub use servers::WorkflowExecutor;pub use servers::WorkflowServer;pub use servers::WorkflowServerConfig;
Modules§
- auth
- Authentication support for MCP communication
- registry
- Server registry for managing multiple MCP servers
- servers
- Built-in MCP servers for common operations
Structs§
- Default
McpClient - MCP client implementation using transport layer
- Http
Transport - HTTP transport for remote MCP servers
- McpRequest
- McpResponse
- Stdio
Transport - Stdio transport - launches MCP server as subprocess
- Tool
Schema
Enums§
Traits§
- McpClient
- Trait for MCP server communication
- McpServer
- Trait for implementing MCP servers
- McpTransport
- Transport layer for MCP communication