Claude-in-Chrome MCP: First tool call always fails, second succeeds

Description

The first tool call to any Claude-in-Chrome MCP server tool always fails with "No such tool available" error, but the second identical call succeeds. This is reproducible across multiple Claude Code sessions.

Steps to Reproduce

1. Start a new Claude Code session with Claude-in-Chrome MCP server configured
2. Call any Claude-in-Chrome tool (e.g., tabs_context_mcp)
3. Observe the error: "No such tool available: mcp__claude-in-chrome__tabs_context_mcp"
4. Call the same tool again
5. The call succeeds

Expected Behavior

The first tool call should succeed, or at minimum Claude Code should handle the initialization transparently.

Actual Behavior

• First call: Fails with "No such tool available" error
• Second call: Works correctly

Likely Cause

This appears to be a lazy initialization issue where:

1. The first call triggers the MCP server connection to actually establish
2. The call fails because the connection isn't ready yet
3. Subsequent calls work because the connection is now warm

Possible Fixes

1. MCP server side: Initialize the connection eagerly on startup rather than on first tool call
2. Claude Code side: Add a retry mechanism for the first MCP call, or perform a warmup ping when the MCP server is registered

Environment

• Claude Code CLI
• Claude-in-Chrome MCP server
• Linux (NixOS)

Additional Context

The /mcp or related status commands may also show the server as "not connected" even when it's actually functional after the first failed call.