- Developers wiring browser control into coding agents
- Teams evaluating MCP-style browser tools
- Builders who want deterministic browser automation primitives
BSD-3-Clause ยท Plugins
Agent Browser Protocol
Deterministic browser automation protocol for Claude, Codex, OpenCode, and MCP-style agent workflows.
0.5K stars 0.0K forks BSD-3-Clause license 2026-06-09 verified
$
# Agent Browser Protocol$
pip install agent-browser-protocol$
npx agent-browser-protocol --help Open sourceMCPAPI
Overview
What is Agent Browser Protocol?
Agent Browser Protocol is an open-source browser automation project that exposes deterministic browser actions for agent tools. It is aimed at developers who want a cleaner control surface between coding agents and a real browser.
Protocol-shaped browser control
The project focuses on a deterministic interface for browser automation.
Protocols make browser capabilities easier to expose to multiple agents without rewriting every integration.Agent-tool compatibility
It is positioned for Claude, Codex, OpenCode, and MCP-style workflows.
A shared browser control layer can reduce glue code across agent environments.Inspectable automation
Deterministic actions are easier to log, replay, and constrain than free-form browser control.
Inspection is important before agents touch authenticated or business-critical web apps. Use cases
What teams use it for
Ecosystem
Tags & capabilities
Comparison
How it stacks up
When to choose Agent Browser Protocol
Compare it with nearby plugins by looking at hosting model, integration surface, license, and whether the official docs show the workflow you need.
FAQ
Questions
Is Agent Browser Protocol open source?
Yes. The repository is listed under the BSD-3-Clause license.
Who should use it?
Developers building browser tools for AI coding agents or MCP-style workflows should evaluate it.
Decision brief
JSON
Should you use Agent Browser Protocol?
- Non-technical users looking for a hosted automation app
- Teams that only need passive page screenshots
- Verified 2026-06-09
- License: BSD-3-Clause
- Repo: theredsix/agent-browser-protocol
- Open-source signal
Deployment
cloud
Permission surface
browser, shell/files, external services
Decision signals
MCP, API
Agent packet
Structured decision data for Agent Browser Protocol
This packet is the compact machine-readable view agents should use before following source links or taking action.
Capabilities
mcp, browser automation, protocol
Constraints
open source, mcp compatible
Deployment
cloud
Permission surface
browser, shell/files, external services
Recommended workflows
Browser automation, Coding agent workflow, Connector or protocol layer
Overview
What Agent Browser Protocol does
What it is
It exposes browser actions to AI agents through a clearer interface than raw ad hoc control.
Why it matters
Browser automation is becoming a common agent capability, and teams need a controllable boundary between the agent and the browser.
How to evaluate it
Evaluate it on a local web app first, then inspect action logs and failure recovery before connecting production accounts.
Facts
Known metadata and operating surface
These fields are separated from editorial interpretation so agents can reason over facts and missing checks.
Resource type plugin
Category Plugins
Maturity active
Difficulty Unknown
License BSD-3-Clause
Pricing open source
Verified 2026-06-09
Source confidence medium
Risk level elevated
Fit matrix
Where Agent Browser Protocol fits in an agent stack
strong
Browser automation
Agent Browser Protocol has multiple signals for browser automation, including matching tags, capabilities, category, or positioning.
- Run one non-sensitive website task and inspect clicks, waits, retries, and changed URLs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong
Coding agent workflow
Agent Browser Protocol has multiple signals for coding agent workflow, including matching tags, capabilities, category, or positioning.
- Run a small repository change and inspect the diff, tests, and rollback path.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong
Connector or protocol layer
Agent Browser Protocol has multiple signals for connector or protocol layer, including matching tags, capabilities, category, or positioning.
- Connect one low-risk service, then inspect schemas, auth scope, errors, and logs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial
Evaluation and observability
Agent Browser Protocol has at least one signal for evaluation and observability, but should be checked against a real task before adoption.
- Add one repeatable test case and confirm results can run again in review or CI.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial
Reusable skill workflow
Agent Browser Protocol has at least one signal for reusable skill workflow, but should be checked against a real task before adoption.
- Run one skill end to end and check whether it produces evidence or structured output.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
weak
Local or private AI stack
Agent Browser Protocol is not primarily positioned for local or private ai stack in the current metadata.
- Verify hardware requirements, data path, storage, and whether all calls stay in your environment.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Inputs and outputs
What an agent should inspect
Likely inputs
- Web pages, DOM state, screenshots, forms, or browser sessions
- Repositories, files, issues, terminal output, and test results
- Tool schemas, API requests, service resources, and auth scopes
- Official setup instructions and a small real workflow
Likely outputs
- Action traces, changed pages, extracted data, or completed browser steps
- Diffs, commits, explanations, test results, or review notes
- Scores, traces, regression results, dashboards, or failure cases
- A decision on whether this resource fits the target workflow
Evidence
Sources, claims, and missing checks
Claims are marked separately from source links so future crawlers and reviewers can update them without rewriting the page.
Agent Browser Protocol is listed as open source.
License metadata: BSD-3-ClauseAgent Browser Protocol has a recorded GitHub repository: theredsix/agent-browser-protocol.
Resource facts and GitHub source link.Agent Browser Protocol supports these recorded deployment modes: cloud.
OpenAgent decision signal metadata.Agent Browser Protocol is tagged with mcp, browser automation, protocol capabilities.
OpenAgent capability taxonomy.- Dedicated docs link is missing.
- Repository freshness has not been recorded.
Next action
How to start evaluating Agent Browser Protocol
Inspect repository
Check license, recent activity, issues, examples, and security-sensitive code paths.
Open source Compare
Alternatives and nearby resources
Use related resources to compare category fit, license, deployment model, and first-workflow behavior.
FAQ
Common questions about Agent Browser Protocol
Is Agent Browser Protocol open source?
Yes. The repository is listed under the BSD-3-Clause license.
Who should use it?
Developers building browser tools for AI coding agents or MCP-style workflows should evaluate it.