v5.8.0 - Function-Based Auto-Approval

[ravitemer]

What's New

Function-Based Auto-Approval

You can now provide a custom function to auto_approve that makes intelligent decisions based on tool arguments.

require("mcphub").setup({
    auto_approve = function(params)
        -- Respect CodeCompanion's auto tool mode when enabled
        if vim.g.codecompanion_auto_tool_mode == true then
            return true -- Auto approve when CodeCompanion auto-tool mode is on
        end
        
        -- Auto-approve GitHub issue reading
        if params.server_name == "github" and params.tool_name == "get_issue" then
            return true -- Auto approve
        end
        
        -- Block access to private repos
        if params.arguments.repo == "private" then
            return "You can't access my private repo" -- Error message
        end
        
        -- Check if tool is configured for auto-approval in servers.json
        if params.is_auto_approved_in_server then
            return true -- Respect servers.json configuration
        end
        
        return false -- Show confirmation prompt
    end,
})

Parameters available in the function:

• params.server_name - Name of the MCP server
• params.tool_name - Name of the tool being called (nil for resources)
• params.arguments - Table of arguments passed to the tool
• params.action - Either "use_mcp_tool" or "access_mcp_resource"
• params.uri - Resource URI (for resource access)
• params.is_auto_approved_in_server - Boolean indicating if tool is configured for auto-approval in servers.json

Return values:

• true - Auto-approve the call
• false - Show confirmation prompt
• string - Deny with error message
• nil - Show confirmation prompt (same as false)

Auto-Approval Priority

The system checks auto-approval in this order:

1. Function: Custom auto_approve function (if provided)

2. Server-specific: autoApprove field in server config (Press a against a tool or server)

3. Default: Show confirmation dialog

Key Benefits

• Argument-based decisions - Approve/deny based on actual tool parameters
• Custom error messages - Return strings for user-friendly denials
• Backward compatible - Existing boolean/server configs still work
• Rich context - Access to server_name, tool_name, arguments, uri, etc.