[BUG] MCP servers connect successfully but tools don't surface as callable, even after full restart

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?

Playwright MCP and Firecrawl MCP both report as connected (confirmed via claude mcp list), but neither exposes any callable tools in the session — not in the initial tool listing, not via deferred-tool search. Persists across a full VS Code restart.

What Should Happen?

A server reporting "Connected" should expose its tools as callable in the same session.

mcp-tool-discovery-bug-log.txt

Error Messages/Logs

[mcp-tool-discovery-bug-log.txt](https://github.com/user-attachments/files/31070434/mcp-tool-discovery-bug-log.txt)

Please see logs provided

Steps to Reproduce

1. Install Playwright MCP and Firecrawl MCP (stdio transport). 2. Confirm both connected via claude mcp list. 3. Search for or try to call a tool from either server — none found. 4. Fully restart VS Code. 5. Issue persists.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

N/A (not confirmed as a regression

Claude Code Version

2.1.231

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

Platform - VS Code Extension
Operating System - Windows 11 Pro, build 10.0.26200
Terminal/Shell - Windows PowerShell 5.1

Separate from the already-filed Meta Ads MCP bug (that one never finishes connecting — HTTP-transport timeout, confirmed still failing in the same mcp list output above). This one is specifically about connected servers exposing no tools.