Greptile Summary

This PR updates the rmcp (Rust Model Context Protocol) crate from version 0.1.5 to 0.6, which represents a major version upgrade with significant API changes. The MCP (Model Context Protocol) is used by Shuttle to provide AI assistants and other tools with structured access to deployment, project management, and logging operations.

The update introduces several key architectural improvements:

1. Constructor Pattern: The ShuttleMcpServer now requires explicit initialization via ShuttleMcpServer::new() instead of direct struct instantiation, following standard Rust patterns.

2. Unified Parameter Handling: All MCP tools now use structured parameter objects (DeployArgs, ProjectStatusArgs, LogsArgs) instead of mixed parameter patterns. This consolidates the cwd (current working directory) parameter into each struct rather than passing it separately.

3. Enhanced Macro System: The update leverages new procedural macros (#[tool_router], #[tool_handler], #[tool]) that reduce boilerplate and provide a more declarative API for defining MCP tools.

4. JSON Schema Integration: All parameter structs now derive schemars::JsonSchema and include descriptive annotations, enabling automatic schema generation for better API documentation and validation.

5. ToolRouter Pattern: The server implementation now uses a centralized ToolRouter for managing tool registration and handling, replacing the previous #[tool(tool_box)] pattern.

The changes maintain all existing functionality while modernizing the codebase to align with rmcp 0.6's improved type safety, reduced boilerplate, and enhanced tooling support. This upgrade positions Shuttle's MCP integration to take advantage of the latest features in the Model Context Protocol ecosystem.

Important Files Changed

Confidence score: 4/5

• This PR represents a well-structured dependency upgrade that maintains functionality while modernizing the API
• Score reflects the systematic nature of changes and consistent patterns across all affected files
• Pay close attention to the workspace Cargo.toml and mcp module integration to ensure no breaking changes in downstream usage

Sequence Diagram

sequenceDiagram
    participant User
    participant ShuttleMcpServer
    participant ToolRouter
    participant Utils
    participant ShuttleCLI as "Shuttle CLI"

    User->>ShuttleMcpServer: "MCP request (deploy/logs/project/docs)"
    ShuttleMcpServer->>ToolRouter: "route_tool(request)"
    ToolRouter->>ShuttleMcpServer: "call appropriate tool method"
    
    alt Deploy Tool
        ShuttleMcpServer->>Utils: "run_tool(deploy(args))"
        Utils->>ShuttleCLI: "execute_command('shuttle', ['deploy', ...], cwd)"
    else Deployment List/Status
        ShuttleMcpServer->>Utils: "run_tool(deployment_list/status(args))"
        Utils->>ShuttleCLI: "execute_command('shuttle', ['deployment', ...], cwd)"
    else Logs Tool
        ShuttleMcpServer->>Utils: "run_tool(logs(args))"
        Utils->>ShuttleCLI: "execute_command('shuttle', ['logs', ...], cwd)"
    else Project Status/List
        ShuttleMcpServer->>Utils: "run_tool(project_status/list(args))"
        Utils->>ShuttleCLI: "execute_command('shuttle', ['project', ...], cwd)"
    else Search Docs
        ShuttleMcpServer->>Utils: "run_tool(search_docs(query))"
        Utils->>ShuttleCLI: "execute_command('shuttle', ['docs', 'search', query], cwd)"
    end
    
    ShuttleCLI-->>Utils: "command output"
    Utils-->>ShuttleMcpServer: "Result<String, String>"
    ShuttleMcpServer-->>ToolRouter: "tool result"
    ToolRouter-->>ShuttleMcpServer: "response"
    ShuttleMcpServer-->>User: "MCP response with CLI output"

_{7 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}