MCP Browser Tabs Server
Pestañas del navegador MCP
Servidor de Protocolo de Contexto de Modelo para recuperar y administrar información de las pestañas del navegador Chrome. Esto permite a Claude Desktop (o a cualquier cliente MCP) obtener información sobre las pestañas abiertas de Chrome y controlarlas.
Inicio rápido (para usuarios)
Para utilizar esta herramienta con Claude Desktop, simplemente agregue lo siguiente a su configuración de Claude Desktop ( ~/Library/Application Support/Claude/claude_desktop_config.json ):
{
"tools": {
"browser-tabs": {
"command": "npx",
"args": ["-y", "@kazuph/mcp-browser-tabs"]
}
}
}Esto descargará y ejecutará automáticamente la última versión de la herramienta cuando sea necesario.
Configuración requerida
Habilitar accesibilidad para Chrome:
Abrir configuración del sistema
Vaya a Privacidad y seguridad > Accesibilidad
Haga clic en el botón "+"
Añade Google Chrome desde tu carpeta de Aplicaciones
Activa el interruptor para Chrome
Esta configuración de accesibilidad es necesaria para que AppleScript interactúe con las pestañas de Chrome.
Related MCP server: chrome-agent-bridge
Para desarrolladores
Las siguientes secciones son para aquellos que quieran desarrollar o modificar la herramienta.
Prerrequisitos
Node.js 18+
macOS (para operaciones de AppleScript)
Google Chrome
Claude Desktop (instalación desde https://claude.ai/desktop )
tsx (instalación mediante
npm install -g tsx)
Instalación
git clone https://github.com/kazuph/mcp-browser-tabs.git
cd mcp-browser-tabs
npm install
npm run buildHerramientas disponibles
get_tabs: Obtiene todas las pestañas abiertas del navegador Google Chrome, devolviendo sus títulos y URL. Las pestañas se agrupan por ventana y se muestran en un formato similar a "Ventana 1-1" (Ventana 1, Pestaña 1).close_tab: cierra una pestaña específica en Google Chrome usando índices de ventana y pestaña.Parámetros:
windowIndex: Número de ventana (comienza desde 1)
tabIndex: Número de pestaña dentro de la ventana (comienza desde 1)
Nota: Al cerrar varias pestañas, comience por los índices más altos para evitar cambios. Después de cerrar las pestañas, use get_tabs para confirmar los cambios.
Notas
Esta herramienta está diseñada solo para macOS debido a su dependencia de AppleScript.
Requiere que Google Chrome esté instalado y en funcionamiento.
Se deben conceder permisos de accesibilidad para Chrome.
Licencia
Licencia MIT: consulte el archivo de LICENCIA para obtener más detalles
Available Tools
4 toolsactivate_tab_by_idA
🔥 PREFERRED METHOD: Activate (focus) a specific tab in Google Chrome using its unique tab ID. Brings the tab to the front and makes it active. Extract the Tab ID from [Tab ID: 1234567890] in get_tabs output.
Inputs: tabId (required).
close_tabA
⚠️ LEGACY DANGER: Close a specific tab using window/tab index. HIGH RISK of closing wrong tabs due to index shifting when tabs are reordered/closed. STRONGLY DEPRECATED: Use close_tab_by_id instead. Only use if Tab ID is unavailable.
Inputs: tabIndex (required), windowIndex (required).
close_tab_by_idA
🔥 PREFERRED METHOD: Close a specific tab in Google Chrome using its unique tab ID. IMMUNE to tab reordering, window changes, and index shifting. Extract the Tab ID from [Tab ID: 1234567890] in get_tabs output. Example: if tab shows '[Tab ID: 1594670961]', use tabId: 1594670961
Inputs: tabId (required).
get_tabsA
Get all open tabs from Google Chrome browser with unique tab IDs. Each tab has a stable, unique ID that persists across browser operations. Output shows both display format (1-1, 1-2) and Tab ID [Tab ID: 1234567890] for each tab. ALWAYS use the Tab ID number for reliable operations.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_tabs retrieves tab information, activate_tab_by_id focuses a tab, close_tab_by_id closes a tab reliably, and close_tab serves as a deprecated fallback. The descriptions explicitly differentiate between preferred and legacy methods, eliminating any ambiguity in tool selection.
All tool names follow a consistent verb_noun or verb_noun_by_id pattern using snake_case (e.g., get_tabs, activate_tab_by_id, close_tab_by_id, close_tab). This uniformity makes the tool set predictable and easy to understand at a glance.
With 4 tools, this server is well-scoped for managing browser tabs, covering essential operations: retrieving tabs, activating them, and closing them (with both reliable and deprecated methods). The count is efficient without being overly sparse or bloated.
The tool set covers the core CRUD-like operations for browser tab management: get (list), activate (update focus), and close (delete). A minor gap exists in creating or opening new tabs, but the domain is focused on existing tab manipulation, and agents can work around this by using external methods if needed.
Maintenance
Related MCP Connectors
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Unofficial Browserless MCP — wraps the Browserless headless-Chromium REST API (browserless.io)
Control your Chrome from chat: open websites, read what's on the page, click buttons, and fill in f…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible agents to securely control the user's already authenticated Chrome browser via explicit tab authorization and DOM-based actions.1Apache 2.0
- AlicenseCqualityBmaintenanceMCP server for agent interaction with user-approved Google Chrome tabs, enabling tab listing/control, navigation, clicking, filling, snapshots, and screenshots via a local authenticated bridge.1004MIT
- FlicenseNot gradedqualityDmaintenanceEnables MCP clients to control real Chrome tabs in existing profiles, supporting navigation, interaction, screenshots, and console/network inspection across multiple Chrome instances.-
- AlicenseNot gradedqualityBmaintenanceEnables local control of existing Chrome/Chromium browser tabs through MCP, including tab management, navigation, content reading, screenshots, and page interaction.Apache 2.0