// Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.
Integrate projects with TabzChrome terminals via Markdown links, HTML attributes, WebSocket, JS API, or Spawn API
Spawn and manage terminal tabs via TabzChrome REST API. Use when spawning workers, creating terminals programmatically, setting up worktrees for parallel work, or crafting prompts for Claude workers.
Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.
Spawn and manage terminal tabs via TabzChrome REST API. Use when spawning workers, creating terminals programmatically, setting up worktrees for parallel work, or crafting prompts for Claude workers.
Integrate projects with TabzChrome terminals via HTML attributes, WebSocket, JS API, or Spawn API
Patterns for building and debugging TabzChrome itself. Use when working on Terminal.tsx, xterm.js integration, WebSocket I/O, resize handling, or any TabzChrome extension/backend code.
| name | tabz-browser |
| description | Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications. |
Control Chrome via MCP tools for screenshots, interaction, debugging, and notifications.
Use mcp-cli to discover and call tools:
# Get tool schema (REQUIRED before calling)
mcp-cli info tabz/tabz_screenshot
# Call tool
mcp-cli call tabz/tabz_screenshot '{}'
# Get current tab info
mcp-cli call tabz/tabz_get_page_info '{}'
# Take screenshot
mcp-cli call tabz/tabz_screenshot '{}'
# Returns file path - use Read tool to view
# 1. Enable capture BEFORE triggering action
mcp-cli call tabz/tabz_enable_network_capture '{}'
# 2. Trigger the action on page
# 3. Get failed requests (status >= 400)
mcp-cli call tabz/tabz_get_network_requests '{"statusMin": 400}'
# 4. Check console for JS errors
mcp-cli call tabz/tabz_get_console_logs '{"level": "error"}'
# Emulate device
mcp-cli call tabz/tabz_emulate_device '{"device": "iPhone 14"}'
# Take screenshot
mcp-cli call tabz/tabz_screenshot '{}'
# Clear emulation
mcp-cli call tabz/tabz_emulate_clear '{}'
mcp-cli call tabz/tabz_fill '{"selector": "#email", "value": "test@example.com"}'
mcp-cli call tabz/tabz_click '{"selector": "button[type=submit]"}'
mcp-cli call tabz/tabz_speak '{"text": "Task complete"}'
mcp-cli call tabz/tabz_profile_performance '{}'
# Returns: DOM nodes, JS heap, event listeners, timing
mcp-cli call tabz/tabz_get_dom_tree '{"maxDepth": 3}'
| Category | Count | Key Tools |
|---|---|---|
| Screenshots | 2 | screenshot, screenshot_full |
| Interaction | 4 | click, fill, get_element |
| Network | 3 | enable_network_capture, get_network_requests |
| DOM/Debug | 4 | get_dom_tree, get_console_logs, profile_performance |
| Emulation | 6 | emulate_device, emulate_geolocation |
| Audio/TTS | 3 | speak, list_voices, play_audio |
| Tabs | 5 | list_tabs, open_url, switch_tab |
| Cookies | 5 | cookies_get, cookies_list |
mcp-cli info tabz/<tool> before callingtabId when possible - don't rely on "active" tab1762561083)tabz_screenshot cannot capture Chrome sidebarSee references/ for detailed workflows:
screenshot-workflows.md - Viewport vs full pagenetwork-debugging.md - API request inspectionform-automation.md - Clicks, fills, selectorstts-notifications.md - Audio feedback patterns