[BUG] MCP connector and constant regression with most database task

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Claude's coding capability seems to be suffering; Sonnet 4.5 is more of a code assistant than truly agentic. The MCP connectors are broken, and there appears to be no real effort from Anthropic to fix them.

Second, Claude 4.5's 'plan mode' is not as well-defined as its new 'thinking' process. I am disappointed that a great product and a fantastic tool is slowly being deprecated for profit.

It's too bad, because Claude for coding was the best. I'm hoping the Gemini 3.0 update will be closer to what I need. I am tired of these updates that create new friction in my workflow. I'm very annoyed and thinking of trying a different route for my projec

What Should Happen?

claude code should be abl;e to connect via mcp to sapabase and the plan features most be back like it was real define planning .

Error Messages/Logs

Steps to Reproduce

⏺ Perfect! MCP is connected. Now let me query your database directly using the MCP Supabase
tools:

⏺ Let me check what MCP tools are actually available and try listing tables first:

⏺ The MCP connection shows as connected but the tools aren't loading. This is the exact bug you
mentioned - recent Claude Code versions have broken MCP tool registration.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.0.10

Claude Code Version

2.0.27

Platform

Other

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_