[FEATURE] Allow MCP tools to access existing tabs without requiring a dedicated MCP tab group

Problem

Currently, Claude Code's claude-in-chrome MCP tools can only interact with tabs inside a dedicated "Claude (MCP)" tab group. When a developer encounters an issue in their browser and wants Claude to inspect it, the workflow is:

1. Call tabs_context_mcp → creates a new Chrome window with an empty MCP tab group
2. Manually drag the relevant tab into that MCP group
3. Only then can Claude see the tab

This defeats the purpose of quick browser inspection. The whole point is to say "look at what I have open" — not to rearrange windows first.

Expected behavior

Claude Code should be able to see and interact with any tab in the user's Chrome browser (with user permission), not just tabs inside the MCP tab group.

Ideal workflow:

1. Developer sees an issue on localhost:5173
2. Types in CLI: "check my browser, the layout is broken"
3. Claude sees the already-open tab and inspects it

Possible approaches

• Allow tabs_context_mcp to list all tabs (or tabs matching a filter), not just MCP group tabs
• Add a tool like tabs_adopt that brings an existing tab into the MCP group programmatically (no manual drag needed)
• Make MCP tab group optional — let tools work with any tab when there's only one CLI session

Related issues

• #16035 — Reuse existing tab group instead of creating new ones
• #23861 — MCP tab groups persist and multiply across sessions
• #19740 — Multi-profile support
• #15193 — Multi-session tab group isolation

Environment

• macOS, Claude Code 2.1.45
• Claude in Chrome extension