MCP stdio adapter for Iris browser automation.
Iris MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP stdio adapter for Iris browser automation.
Iris is an open-source Chrome extension and local browser automation runtime for OpenCode. It lets OpenCode agents inspect and control the browser you actually use, with your real tabs, cookies, downloads, console logs, and authenticated sessions.
You will need 2 environment variables: IRIS_EXTENSION_ID, OPENCODE_BROWSER_EXTENSION_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by mizner; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Iris's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
Example MCP config:
```json
{
"mcpServers": {
"iris": {
"command": "node",
"args": ["/absolute/path/to/iris/packages/mcp/dist/server.js"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| IRIS_EXTENSION_ID | Configuration value read at startup. | Optional |
| OPENCODE_BROWSER_EXTENSION_ID | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.