opencode-browser
Provides an OpenCode plugin that integrates the Browser MCP (browsermcp) to let an AI agent drive a Chrome/Edge browser for automation tasks such as navigation, clicking, form filling, scraping, and screenshot/snapshot-based verification—primarily via MCP tool calls.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No explicit security controls are documented at the plugin level (no scopes, no per-domain allowlists, no credential handling). The approach controls a real browser via a local MCP server/extension, which increases risk if used with sensitive sites without additional guardrails. README mentions an environment variable (BROWSER_MCP_DEBUG) but does not discuss secret storage/redaction practices. Dependency data is not provided in the manifest, so dependency hygiene cannot be fully verified.
⚡ Reliability
Best When
When you already use OpenCode and want an agent to control a real browser via Browser MCP (Chrome/Edge) with guidance that reduces unnecessary tool calls.
Avoid When
When you need fine-grained audit/logging, strict access control for specific pages/actions, or a documented, standalone API for external systems beyond OpenCode.
Use Cases
- • Automated browser-based testing flows in an OpenCode agent
- • Web scraping of page content and extraction of structured data
- • Automated form filling and submission (e.g., contact/login flows in test environments)
- • End-to-end UI checks with screenshots/snapshots for verification
- • Assisted browser navigation from natural-language prompts within OpenCode
Not For
- • Direct production use for sensitive accounts without additional security review
- • Fully offline operation where a browser extension and MCP runtime cannot be started
- • High-integrity automation requiring strict idempotency and transactional safety
- • Use cases that require a public REST/HTTP API contract independent of OpenCode
Interface
Authentication
No authentication mechanism is described for this plugin itself; it relies on the local Browser MCP server/extension and OpenCode configuration. Any authentication/authorization model would be handled by OpenCode and/or the Browser MCP extension/server.
Pricing
README does not describe pricing/tiers. Browser automation itself may incur compute/agent usage costs in OpenCode and MCP runtime costs locally.
Agent Metadata
Known Gotchas
- ⚠ Browser state can change between attempts; ensure selectors/actions are specific to avoid unintended interactions
- ⚠ Snapshots/screenshots/waits are described as slower; agents should minimize these unless needed
- ⚠ Connection issues are addressed with immediate retry guidance, but success depends on extension/browser readiness
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for opencode-browser.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.