Permite la automatización de navegadores impulsada por IA dentro del editor OpenCode para navegar por sitios web, completar formularios y extraer datos usando Chrome o Edge.
También conocido como michaljach/opencode-browser
- Stars
- 119
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 15 oct 2026
- Licencia
- MIT
¿Qué es opencode-browser MCP?
Permite la automatización de navegadores impulsada por IA dentro del editor OpenCode para navegar por sitios web, completar formularios y extraer datos usando Chrome o Edge.
Resumen generado a partir del README del proyecto
Acerca del MCP server de opencode-browser
Automatizar tareas web directamente desde tu editor es posible con opencode-browser, que lleva el control del navegador a los usuarios de OpenCode. Este plugin permite que una IA navegue por sitios web, interactúe con formularios y extraiga datos controlando los navegadores Chrome o Edge. Está diseñado para desarrolladores que utilizan OpenCode 1 (versión 1.18.29+) o OpenCode 2 y necesitan cerrar la brecha entre su entorno de programación y el contenido web en vivo.
Para usar esta herramienta, debes tener instalado Node.js y la extensión Browser MCP activa en tu navegador. La configuración implica configurar tu archivo opencode.json para ejecutar el MCP server local mediante npx. El plugin se distingue por inyectar instrucciones orientadas a la velocidad en el prompt del modelo, lo que incentiva a la IA a utilizar la navegación directa y minimizar acciones costosas como tomar capturas de pantalla o snapshots de la página completa. También cuenta con un comportamiento de reintento rápido que evita retrasos artificiales cuando se interrumpe la conexión con el navegador.
Qué puedes hacer con él
- 1Web scraping automatizadoExtraer información específica de un sitio web, como titulares de noticias o listas de productos.
- 2Automatización de formularios webIndicar a la IA que navegue hasta una página de contacto y envíe detalles específicos del usuario.
- 3Ejecución de flujos de trabajo complejosRealizar secuencias de múltiples pasos que incluyen iniciar sesión en cuentas y capturar evidencia visual de un dashboard.
- 4Navegación dirigida en sitios webDirigir a la IA a una URL específica para realizar una búsqueda sin necesidad de clics manuales.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar opencode-browser MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar opencode-browser MCP en Claude Code
$ claude mcp add opencode-browser -- npx -y opencode-browserInstalar opencode-browser MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"opencode-browser": {
"command": "npx",
"args": [
"-y",
"opencode-browser"
]
}
}
}Instalar opencode-browser MCP en VS Code
.vscode/mcp.json
{
"servers": {
"opencode-browser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"opencode-browser"
]
}
}
}Instalar opencode-browser MCP en VS Code CLI
$ code --add-mcp '{"name":"opencode-browser","type":"stdio","command":"npx","args":["-y","opencode-browser"]}'Instalar opencode-browser MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"opencode-browser": {
"command": "npx",
"args": [
"-y",
"opencode-browser"
]
}
}
}Instalar opencode-browser MCP en Codex
$ codex mcp add opencode-browser -- npx -y opencode-browserInstalar opencode-browser MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.opencode-browser] command = "npx" args = ["-y", "opencode-browser"]
Instalar opencode-browser MCP en Gemini CLI
$ gemini mcp add -s user opencode-browser npx -- -y opencode-browserInstalar opencode-browser MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"opencode-browser": {
"command": "npx",
"args": [
"-y",
"opencode-browser"
]
}
}
}Configuración
BROWSER_MCP_DEBUG
| Nombre | Descripción | Tipo |
|---|---|---|
| BROWSER_MCP_DEBUG | — |
Verificaciones automáticas
Ejecutado 12 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleAprobado
- Licencia de código abierto (OSI)Aprobado
- Commit o lanzamiento en el último añoAprobado
- El nombre del paquete no es similar a un paquete popularAprobado
- El endpoint remoto usa HTTPSNo verificado
- Las herramientas destructivas están etiquetadasNo verificado
- Sin instrucciones ocultas para el modeloAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
README
Ver en GitHubOpenCode Browser MCP Plugin
An OpenCode plugin that integrates Browser MCP to enable browser automation capabilities within OpenCode. This plugin allows the AI to control a browser, navigate websites, fill forms, click elements, and perform other browser automation tasks.
Works with both OpenCode 1 (1.18.29+) and OpenCode 2.
Demo

Features
- Full browser automation support through Browser MCP
- OpenCode 1 and 2 support from one package
- Speed-oriented browser guidance injected into the model prompt
- Tool-specific performance hints for expensive browser actions
- Fast retry behavior with no artificial reconnect backoff in the plugin
- Automatic detection of browser-related tasks
- Context preservation for browser state across session compactions
- Seamless integration with OpenCode's existing tools
Prerequisites
Before using this plugin, you need:
- Node.js installed on your system
- OpenCode 1.18.29+ or OpenCode 2 installed and configured
- Browser MCP extension installed in your browser (Chrome/Edge)
Installation
Step 1: Install Browser MCP Extension
- Visit https://browsermcp.io/install
- Install the Browser MCP extension for your browser (Chrome or Edge)
- Follow the extension setup instructions
Step 2: Configure OpenCode
Fastest path:
npx opencode-browser init
This creates or updates ./opencode.json with the required plugin and mcp.browsermcp entries while preserving any unrelated config you already have.
For a global setup instead of a project-local one:
npx opencode-browser init --global
If you prefer to preview the generated config without writing it yet:
npx opencode-browser init --print
Or configure it by hand. Create or update your opencode.json configuration file. You can create this file in one of two locations:
- Global configuration (applies to all projects):
~/.config/opencode/opencode.json - Project-specific configuration (applies to current project only):
./opencode.json(in your project root)
Learn more about OpenCode configuration at https://opencode.ai/docs/config
Add this configuration to your opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["opencode-browser"],
"mcp": {
"browsermcp": {
"type": "local",
"command": ["npx", "-y", "@browsermcp/mcp@0.1.3"],
"enabled": true
}
}
}
This configuration does two things:
- Installs the plugin - OpenCode automatically downloads
opencode-browserfrom npm - Configures Browser MCP - Sets up the MCP server that actually controls the browser
That's it! No manual file copying required. OpenCode handles everything automatically.
The generated command pins the Browser MCP package version to avoid the extra @latest resolution step on startup and keep launches reproducible.
OpenCode 2
The plugin ships a single package that supports both OpenCode 1 and OpenCode 2. OpenCode 2 reads the plugin's V2 definition and registers the same guidance through its session, tool, and event APIs; existing plugin configuration keeps working because OpenCode 2 normalizes V1 configuration.
To use the native V2 configuration shape, move the entry from plugin to plugins and use the V2 MCP shape:
{
"$schema": "https://opencode.ai/config.json",
"plugins": ["opencode-browser"],
"mcp": {
"servers": {
"browsermcp": {
"type": "local",
"command": ["npx", "-y", "@browsermcp/mcp@0.1.3"],
"disabled": false
}
}
}
}
No runtime dependencies are required: the plugin's imports of the OpenCode plugin type packages are type-only, so it loads under both APIs without installing @opencode/plugin or @opencode-ai/plugin into the plugin folder.
If OpenCode 2 reports Plugin must export a default definition with an id and an effect or setup function, you are running a version older than 1.3.0. Update the plugin (opencode plugin update, or clear OpenCode's package cache) and restart.
Alternative: Install Locally (for development/testing)
If you want to modify the plugin or test changes:
OpenCode 2: point the config at your clone. The path must be the package directory, not src/index.ts:
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["file:///absolute/path/to/opencode-browser"]
}
OpenCode 1, global installation:
mkdir -p ~/.config/opencode/plugins
cp src/index.ts ~/.config/opencode/plugins/browser-mcp.ts
OpenCode 1, project-specific installation:
mkdir -p .opencode/plugins
cp src/index.ts .opencode/plugins/browser-mcp.ts
The plugin will be automatically loaded on OpenCode startup.
Configuration
Basic Configuration
The minimal configuration requires only the MCP server setup:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"browsermcp": {
"type": "local",
"command": ["npx", "-y", "@browsermcp/mcp@0.1.3"],
"enabled": true
}
}
}
Advanced Configuration
For more control, you can disable Browser MCP tools globally and enable them per agent:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"browsermcp": {
"type": "local",
"command": ["npx", "-y", "@browsermcp/mcp@0.1.3"],
"enabled": true
}
},
"tools": {
"browsermcp_*": false
},
"agent": {
"browser-agent": {
"tools": {
"browsermcp_*": true
}
}
}
}
Performance Behavior
The plugin improves Browser MCP speed by shaping how the model uses browser tools:
- Adds system guidance that prefers direct navigation and fewer browser calls
- Annotates expensive tools like snapshots, screenshots, and waits with performance hints
- Preserves fast-resume guidance during session compaction
- Avoids plugin-side reconnect delays so you can retry immediately when the browser extension is ready
Environment Variables
If you need to pass environment variables to the Browser MCP server:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"browsermcp": {
"type": "local",
"command": ["npx", "-y", "@browsermcp/mcp@0.1.3"],
"enabled": true,
"environment": {
"BROWSER_MCP_DEBUG": "true"
}
}
}
}
Usage
Once installed and configured, you can use browser automation in your OpenCode prompts:
Basic Browser Navigation
Navigate to https://github.com and search for "opencode"
Form Filling
Go to the contact form at https://example.com/contact and fill in:
- Name: John Doe
- Email: john@example.com
- Message: Hello from OpenCode!
Then submit the form.
Web Scraping
Visit https://news.ycombinator.com and get the titles of the top 5 stories
Complex Automation
Go to https://example.com/login, log in with the test credentials,
navigate to the dashboard, and screenshot the main metrics panel
Prompt Tips
For best results when using browser automation:
- Be specific about URLs and actions
- Prefer direct URLs instead of clicking through intermediate pages
- Reuse page state instead of rechecking the same screen repeatedly
- Ask for verification only when needed because snapshots and screenshots are slower than targeted extraction
- Specify selectors when needed (CSS selectors, text content, etc.)
You can also add browser automation guidelines to your AGENTS.md file:
## Browser Automation
When performing browser automation tasks:
- Always confirm the page has loaded before interacting
- Use descriptive selectors (prefer text content over CSS selectors)
- Take screenshots when verification is needed
- Handle errors gracefully (page not found, element not visible, etc.)
- Close tabs when the task is complete
Plugin Features
Speed-Oriented Guidance
The plugin biases the model toward faster browser workflows:
- Prefers direct
navigatecalls when the destination URL is known - Reuses the current tab and page state instead of redoing navigation
- Minimizes
snapshot,screenshot, andwaitcalls unless they are actually needed - Encourages targeted extraction and direct actions over broad inspection
Lightweight Connection Recovery
The plugin still detects browser connection issues, but it no longer adds artificial retry sleeps:
- Detects common Browser MCP connection failures from tool output
- Adds immediate retry guidance to the result instead of pausing inside the plugin
- Marks the connection as restored after the next successful browser action
Automatic Browser Tool Detection
The plugin automatically detects when Browser MCP tools are being used and applies browser-specific guidance.
Session Context Preservation
During session compaction, the plugin preserves browser automation context, ensuring the AI remembers:
- Browser interactions that occurred
- Current browser state considerations
- Fast-resume guidance so it can avoid repeating navigation and inspection
Tool Definition Hints
The plugin annotates Browser MCP tool definitions with performance notes, especially for slower tools like snapshots, screenshots, and waits.
Troubleshooting
Browser MCP Connection Lost
If you see connection errors:
- Check extension status: Verify the Browser MCP extension is enabled in Chrome
- Re-enable extension: If you disabled it, simply re-enable it and retry the browser action immediately
- Check browser is running: Ensure Chrome/Edge is actually running
- Retry after readiness: The plugin does not add extra backoff delay, so the next attempt can run right away
- Restart only if needed: Restart OpenCode only if the browser stays unavailable after retrying
The plugin will display messages like:
[Browser MCP] The browser connection looks unavailable. Re-enable the Browser MCP extension or browser, then retry.[Browser MCP] Connection restored. Continuing without extra retry delay.
Browser MCP Not Working
- Check extension is installed: Open your browser and verify the Browser MCP extension is installed and enabled
- Verify MCP server config: Ensure your
opencode.jsonhas the correct MCP configuration - Check Node.js: Ensure Node.js is installed:
node --version - Test MCP connection: Restart OpenCode after adding the MCP configuration
Plugin Not Loading
- Check the version: OpenCode 2 needs
opencode-browser1.3.0 or newer - Check file location: Ensure the plugin file is in the correct directory. On OpenCode 2, a
file://plugin path must point to the package directory - Check file name: Plugin files should end in
.tsor.js - Check syntax: Ensure the TypeScript/JavaScript syntax is valid
- Check logs: Look for plugin initialization messages in OpenCode output
Tools Not Available
- Check MCP server status: Ensure the Browser MCP server started successfully
- Check tool configuration: Verify tools aren't disabled in your config
- Restart OpenCode: Try restarting OpenCode after configuration changes
Debug Mode
Enable debug logging by modifying the plugin or checking OpenCode logs:
# OpenCode 2: print server logs while running a prompt
opencode run --standalone --print-logs --log-level debug "your prompt"
# OpenCode 1
opencode --verbose
Development
Building from Source
If you want to modify the plugin:
- Clone the repository
- Make your changes to
src/index.ts - Run
npm run typecheckandnpm test(covers both the OpenCode 1 and OpenCode 2 entrypoints) - Test locally with a
file://plugin path (see Install Locally) - Submit a PR if you'd like to contribute!
Plugin Architecture
The package default-exports one definition with two entrypoints that share the same state and guidance text: id + setup() for OpenCode 2, and server() for OpenCode 1.
| Purpose | OpenCode 1 hook | OpenCode 2 API |
|---|---|---|
| Inject speed-oriented browser guidance | experimental.chat.system.transform |
ctx.session.hook("context") |
| Add performance hints to Browser MCP tools | tool.definition |
ctx.tool.transform |
| Post-process browser tool results | tool.execute.after |
ctx.tool.hook("execute.after") |
| Preserve browser context | experimental.session.compacting |
ctx.session.hook("compaction") |
| Clean up session state | event |
ctx.event.subscribe() |
On OpenCode 2, browser tools called from Code Mode are reported on the execute result's nested toolCalls, which the plugin also reads so connection recovery hints still work.
Contributing
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request
Resources
License
MIT License - See LICENSE file for details
Support
For issues and questions:
- Browser MCP issues: Browser MCP GitHub
- OpenCode issues: OpenCode GitHub
- Plugin issues: Open an issue in this repository
Changelog
See CHANGELOG.md for a detailed list of changes in each version.
Preguntas sobre opencode-browser MCP
¿Cómo agrego opencode-browser MCP a Claude Code?
Ejecuta claude mcp add opencode-browser -- npx -y opencode-browser en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego opencode-browser MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué navegadores son compatibles?
El plugin funciona con Google Chrome y Microsoft Edge.
¿Cómo instalo el plugin en OpenCode?
Puedes usar el comando 'npx opencode-browser init' para crear o actualizar automáticamente tu archivo de configuración.
¿Funciona con OpenCode 2?
Sí, el plugin es un paquete único que es compatible tanto con OpenCode 1 como con OpenCode 2.