browser
TabzChrome Browser Automation
Control Chrome via MCP tools for screenshots, interaction, debugging, and notifications.
Quick Start
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 '{}'
Core Workflows
Screenshot a Page
More from ggprompts/tabzchrome
reviewing-code
Code review checkpoint using codex review CLI. Returns structured result with pass/fail status and issues. Use when: 'code review', 'review changes', 'codex review', 'check my code'.
5tabz-development
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.
2tabz-terminals
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.
1tabz-integration
Integrate projects with TabzChrome terminals via HTML attributes, WebSocket, JS API, or Spawn API
1tabz-browser
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.
1terminals
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.
1