Key Takeaways
- Cline v4.1.15 fixes the MCP auto-approve toggle to govern all tools.
- Update your SDK bundle to stop silent no-ops and speed up workflows.
What Changed
Cline v4.1.15 (released via the SDK bundle) fixes a frustrating bug in MCP tool handling. The "Use MCP servers" toggle now auto-approves every MCP tool call when enabled. Previously, the toggle only applied to tools that had also been individually opted in—so flipping it on appeared to do nothing for most users.
This lands through the SDK bundle, meaning it affects all windows running that bundle. If you're using Cline with Claude Code or other SDK-based integrations, this fix is live as soon as you update.
What It Means For You
If you've been manually approving every MCP tool call despite having the "Use MCP servers" toggle on, this is the fix you've been waiting for. The toggle now works as intended: one switch, full auto-approval for all MCP tools.
This is a significant workflow improvement for developers who rely on MCP servers for frequent operations like file reads, database queries, or API calls. Instead of clicking "approve" dozens of times per session, you can enable the toggle and let the agent run uninterrupted.
But be aware: auto-approval means the agent can execute any tool exposed by your MCP servers without asking. This is powerful but risky if you have servers with destructive operations (e.g., delete, write, or deploy). Make sure your MCP servers are trusted and configured with least-privilege principles.
Try It Now
- Update your SDK bundle to v4.1.15 or later. If you're using Cline through a package manager, run the update command (e.g.,
npm update @cline/cline-sdkor your equivalent). - Enable the toggle: In Cline's settings, turn on "Use MCP servers."
- Test it: Trigger a task that uses an MCP tool. You should see no approval prompt—the call executes automatically.
- Audit your MCP servers: List all tools with
cline mcp list(or your SDK's equivalent) and disable any that are dangerous or unnecessary. Consider using read-only servers where possible.
If you're using Claude Code alongside Cline, remember that Claude Code has its own MCP approval settings (/mcp command). This fix is specific to Cline, but the principle applies: review your approval config to avoid surprises.
Related Context
This fix comes amid broader MCP ecosystem changes. The 2026-07-28 MCP spec removed sessions and the initialize handshake, pushing toward statelessness. That shift means tools are more independent, making auto-approval safer—but also more critical to audit. Our earlier article on MCP 2.0 breaking local servers highlights why version pinning matters here.
Also note the community trend toward MCP minimalism: fewer servers reduce context bloat. Auto-approval doesn't change that advice—it just makes your existing setup faster.
Bottom Line
Cline v4.1.15 is a small but impactful fix. If you've been fighting the toggle, update now and reclaim those lost clicks. Just make sure your MCP servers are trustworthy before enabling full auto-approval.
Source: github.com
