🎉 v5.6.0 - Fine-Grained Auto-Approval!

[ravitemer]

We're excited to announce v5.6.0 with Fine-Grained Auto-Approval! 🚀

🎯 Smart Auto-Approval Control

Previously, auto-approval was all-or-nothing. Now you have granular control over which servers and tools get auto-approved, making your workflow both secure and efficient.

⚡ Quick Overview

• Server-level control: Auto-approve all tools on trusted servers
• Tool-specific control: Auto-approve only specific tools you trust
• Visual indicators: See auto-approval status at a glance
• UI toggles: Use a keymap to toggle auto-approval directly from the Hub

🛠️ Configuration Examples

Trust Entire Servers

{
    "mcpServers": {
        "trusted-server": {
            "command": "npx",
            "args": ["safe-mcp-server"],
            "autoApprove": true  // ✅ Auto-approve ALL tools on this server
        }
    }
}

Selective Tool Approval

{
    "mcpServers": {
        "mixed-server": {
            "command": "npx", 
            "args": ["some-mcp-server"],
            "autoApprove": ["read_file", "list_files"]  // ✅ Only these tools
        }
    }
}

⚙️ Configuration in Action

🎮 Interactive Controls

Use the a keymap in the Hub UI to toggle auto-approval:

• Press a on a server line → Toggle auto-approval for all tools on that server
• Press a on a tool line → Toggle auto-approval for just that specific tool

📋 Auto-Approval Priority

The system checks auto-approval in this order:

1. Global: vim.g.mcphub_auto_approve = true (approves everything)
2. Server-specific: autoApprove field in your config
3. Default: Show confirmation dialog

🔒 Security Notes

• Resources are always auto-approved (they're read-only and safe)
• Only enabled servers/tools can be auto-approved

No breaking changes! Your existing auto_approve = true configuration continues to work exactly as before. The new fine-grained controls are purely additive.