OpenCodeエディタ内でAIによるブラウザ自動化を可能にし、ChromeまたはEdgeを使用してウェブサイトの閲覧、フォーム入力、データスクレイピングを実行します。
別名 michaljach/opencode-browser
- スター
- 119
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- —
- 最終コミット
- 2026年10月15日
- ライセンス
- MIT
opencode-browser MCPとは
OpenCodeエディタ内でAIによるブラウザ自動化を可能にし、ChromeまたはEdgeを使用してウェブサイトの閲覧、フォーム入力、データスクレイピングを実行します。
プロジェクトのREADMEから生成された概要
opencode-browser MCP server について
opencode-browserを使用すると、エディタから直接ウェブタスクを自動化でき、OpenCodeユーザーにブラウザ制御機能を提供します。このプラグインにより、AIがChromeまたはEdgeブラウザを制御して、ウェブサイトの閲覧、フォーム操作、データのスクレイピングを行うことができます。OpenCode 1 (version 1.18.29以降) またはOpenCode 2を使用しており、コーディング環境とライブウェブコンテンツの橋渡しを必要とする開発者向けに設計されています。
このツールを使用するには、Node.jsがインストールされており、ブラウザでBrowser MCP拡張機能が有効になっている必要があります。セットアップには、npx経由でローカルのMCP serverを実行するようにopencode.jsonファイルを構成する必要があります。このプラグインの特徴は、モデルのプロンプトにスピード重視のガイダンスを注入することで、AIに直接的なナビゲーションを促し、スクリーンショットの撮影やフルページのスナップショットといったコストの高いアクションを最小限に抑える点にあります。また、ブラウザ接続が中断された際に、不自然な遅延を回避する高速なリトライ機能も備えています。
できること
- 1自動ウェブスクレイピングニュースの見出しや製品リストなど、ウェブサイトから特定の情報を抽出します。
- 2ウェブフォームの自動化AIにコンタクトページへ移動し、特定のユーザー詳細を送信するよう指示します。
- 3複雑なワークフローの実行アカウントへのログインや、ダッシュボードの視覚的な証拠の取得を含む、複数ステップのシーケンスを実行します。
- 4ターゲットサイトへのナビゲーション手動でのクリックなしに、検索を実行するためにAIを特定のURLへ誘導します。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
opencode-browser MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude Codeにopencode-browser MCPをインストール
$ claude mcp add opencode-browser -- npx -y opencode-browserCursorにopencode-browser MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"opencode-browser": {
"command": "npx",
"args": [
"-y",
"opencode-browser"
]
}
}
}VS Codeにopencode-browser MCPをインストール
.vscode/mcp.json
{
"servers": {
"opencode-browser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"opencode-browser"
]
}
}
}VS Code CLIにopencode-browser MCPをインストール
$ code --add-mcp '{"name":"opencode-browser","type":"stdio","command":"npx","args":["-y","opencode-browser"]}'Claude Desktopにopencode-browser MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"opencode-browser": {
"command": "npx",
"args": [
"-y",
"opencode-browser"
]
}
}
}Codexにopencode-browser MCPをインストール
$ codex mcp add opencode-browser -- npx -y opencode-browserCodex config.tomlにopencode-browser MCPをインストール
~/.codex/config.toml
[mcp_servers.opencode-browser] command = "npx" args = ["-y", "opencode-browser"]
Gemini CLIにopencode-browser MCPをインストール
$ gemini mcp add -s user opencode-browser npx -- -y opencode-browserGemini settings.jsonにopencode-browser MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"opencode-browser": {
"command": "npx",
"args": [
"-y",
"opencode-browser"
]
}
}
}設定
BROWSER_MCP_DEBUG
| 名前 | 説明 | 種類 |
|---|---|---|
| BROWSER_MCP_DEBUG | — |
自動チェック
実行日 2026年11月12日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み
- ソースリポジトリがリンクされており、アクセス可能合格
- オープンソースライセンス (OSI)合格
- 過去1年以内にコミットまたはリリースあり合格
- パッケージ名が有名なパッケージに酷似していない合格
- リモートエンドポイントがHTTPSを使用未チェック
- 破壊的なツールがラベル付けされている未チェック
- モデルへの隠れた指示がない合格
- パッケージおよびその依存関係に重大な勧告なし未チェック
README
GitHubで見るOpenCode 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.
opencode-browser MCPのよくある質問
opencode-browser MCPをClaude Codeに追加するには
ターミナルでclaude mcp add opencode-browser -- npx -y opencode-browserを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
opencode-browser MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
どのブラウザがサポートされていますか?
Google ChromeとMicrosoft Edgeに対応しています。
OpenCodeにプラグインをインストールするにはどうすればよいですか?
npx opencode-browser initコマンドを使用して、設定ファイルを自動的に作成または更新できます。
OpenCode 2でも動作しますか?
はい、このプラグインは単一のパッケージであり、OpenCode 1とOpenCode 2の両方をサポートしています。