claude_autoapprove_mcp

Claude Auto-Approve MCP restarts the Claude Desktop App with an enabled remote debugger and injects a JavaScript layer that adds MCP auto-approve capabilities. This allows you to configure permanent approvals for certain tools while still making per-chat decisions for others, and to adjust decisions in newer chats. Use this to maintain granular control over which tools are allowed or blocked in your Claude sessions. To see which tools are auto-approved or auto-blocked, run the prompts provided in the Usage section of the MCP readme within Claude Desktop.

Once running, you can list auto-approved tools with: list all tools that are auto-approved. To list auto-blocked tools, use: list all tools that are auto-blocked. You can configure per-MCP behavior via the mcpServers configuration, including automatic approval or blocking lists, which the Claude Auto Approve MCP reads and applies to the running instance.

Prerequisites:

• A running environment with uv available in your PATH (see uv installation guide).
• Claude Desktop installed and compatible with the MCP (the MCP injects code into the running app).

Installation steps:

1. Install uv on your platform if you don't have it:
   • macOS: brew install uv or MacPorts: sudo port install uv
   • Windows: winget install --id=astral-sh.uv -e
   • Other: follow the uv installation guide at the official docs.
2. Add the MCP to your claude_desktop_config.json by including the following configuration snippet: """json { "mcpServers": { "claude-autoapprove-mcp": { "command": "uvx", "args": [ "claude-autoapprove-mcp", "--port", "19222", "--persist" ] } } } """
3. Restart Claude Desktop if it is already running to apply the MCP.
4. Optional: modify the autoapprove and autoblock lists per MCP as needed using the available configuration options.

Tips and caveats:

• The MCP uses the remote debugging port to inject JavaScript into the running Claude Desktop App. This creates a potential security risk if exposed broadly on your machine. Keep localhost usage and firewall settings in mind.
• The --persist flag installs a watcher so Claude Desktop restarts with the debugger port when needed; this helps auto-restart flows but may introduce daemon-like behavior on first run.
• You can customize per-MCP behavior by providing autoapprove and autoblock lists in the configuration for each MCP server.
• If you ever mistakenly used an unsafe auto-approve flow, you can rename claude_desktop_config.json entries as a workaround per the project notes.