Run AI coding agents with agentic workflows, knowledge packs, and real browser control. Connect Claude Code, Codex, Cursor, ChatGPT, or any MCP
Run AI coding agents with agentic workflows, knowledge packs, and real browser control. Connect Claude Code, Codex, Cursor, ChatGPT, or any MCP client. Exposed over MCP by the sidebutton mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
run_workflow — Execute a workflow by IDget_run_log — Get execution log for a runlist_workflows — List all available workflowsget_workflow — Get workflow YAML definitionlist_run_logs — List recent workflow executionspublish_artifact — Publish evidence (screenshots, reports) from a sessionget_browser_status — Check browser extension connectioncapture_page — Capture selectors from current pagenavigate — Navigate browser to URLsnapshot — Get page accessibility snapshotclick — Click an elementtype — Type text into an elementInstallation goes through your MCP client rather than a global install: point it at sidebutton on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: OPENAI_API_KEY, ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Sidebutton's toolset — run_workflow, get_run_log, list_workflows and 11 more — is a fair guide to whether it matches your workflow. It is maintained by sidebutton; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Sidebutton's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| run_workflow | Execute a workflow by ID |
| get_run_log | Get execution log for a run |
| list_workflows | List all available workflows |
| get_workflow | Get workflow YAML definition |
| list_run_logs | List recent workflow executions |
| publish_artifact | Publish evidence (screenshots, reports) from a session |
| get_browser_status | Check browser extension connection |
| capture_page | Capture selectors from current page |
| navigate | Navigate browser to URL |
| snapshot | Get page accessibility snapshot |
| click | Click an element |
| type | Type text into an element |
| press_key | Send keyboard keys |
| scroll | Scroll the page |
{
"mcpServers": {
"sidebutton": {
"command": "npx",
"args": ["-y", "sidebutton"],
"env": {
"OPENAI_API_KEY": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
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.