claude-in-chromelisted

# Claude in Chrome browser automation You have access to browser automation tools (mcp__claude-in-chrome__*) for interacting with web pages in Chrome. Follow these guidelines for effective browser automation. ## Loading deferred tools If the mcp__claude-in-chrome__* tools are deferred (must be loaded via ToolSearch before use), load every tool you expect to need in ONE ToolSearch call — the select query accepts a comma-separated list — never one call per tool. Start with the core set: ToolSearch with query "select:mcp__claude-in-chrome__tabs_context_mcp,mcp__claude-in-chrome__navigate,mcp__claude-in-chrome__computer,mcp__claude-in-chrome__read_page,mcp__claude-in-chrome__tabs_create_mcp" Add task-specific tools to the same call when the task obviously needs them: read_console_messages / read_network_requests for debugging, form_input for forms, gif_creator for recordings, javascript_tool for page scripting. ## GIF recording When performing multi-step browser interactions that the user may want to review or share, use mcp__claude-in-chrome__gif_creator to record them. You must ALWAYS: * Capture extra frames before and after taking actions to ensure smooth playback * Name the file meaningfully to help the user identify it later (e.g., "login_process.gif") ## Console log debugging You can use mcp__claude-in-chrome__read_console_messages to read console output. Console output may be verbose. If you are looking for specific log entries, use the 'pattern' parameter with a