Use your existing Firefox and logged-in tabs, limited to tabs or groups you explicitly share.
Typed browser control for AI agents, built around explicit capabilities, semantic snapshots, and observable action outcomes.
Zamery Browser lets an agent work with a browser through a provider-neutral contract instead of coupling the agent to one automation engine. The Firefox provider connects to the user's already-running Firefox rather than launching a disposable browser profile.
npm install @zamery/browser-provider @zamery/pi-browser @zamery/browser-firefox
Node.js >=22.19.0 <25 is currently supported. @zamery/pi-browser is tested against @earendil-works/pi-coding-agent@0.87.1.
| Package | Purpose |
|---|---|
@zamery/browser-provider | Provider-neutral BrowserProvider V1/V2 contracts, plus optional bounded browser-asset contracts. |
@zamery/pi-browser | Typed Pi tools for status, contexts, semantic snapshots, browser-backed assets, and actions. |
@zamery/browser-firefox | Firefox provider, Native Messaging host, setup/doctor CLI and the Firefox companion for an already-running Firefox session. |
@zamery/browser-mcp | Standalone stdio MCP server (for Codex and other local MCP hosts): share chosen tabs/tab groups, snapshots, DOM actions, takeover/resume, screenshots. |
AI / Pi agent Codex / local MCP host
| |
@zamery/pi-browser @zamery/browser-mcp
| |
+-- BrowserProvider V2 + optional interfaces --+
|
@zamery/browser-firefox
|
Native Messaging + signed companion
|
Your existing Firefox
The provider contract is intentionally separate from the Firefox implementation. Another browser/provider can implement the same contract without changing the agent-facing tool layer.
import { createBrowserProviderV2 } from "@zamery/browser-firefox";
const provider = createBrowserProviderV2();
try {
const instances = await provider.listInstances();
console.log(instances);
} finally {
await provider.close();
}
For Pi integrations, @zamery/pi-browser exposes browser_status, browser_contexts, browser_snapshot, browser_assets, and browser_act. browser_assets returns opaque refs and safe metadata rather than source URLs or browser credentials.
@zamery/browser-mcp lets a local agent work in the Firefox you already use — logged in, no relaunch, no cookie export — on only the tabs or tab groups you choose to share, for a time you choose (this session, or 1–30 days). You can take over at any time; the agent can only ask to resume. See packages/browser-mcp, the security model and the evidence-backed release status.
Official MCP Registry: io.github.maemreyo/zamery-browser. Firefox Companion: AMO public listing.
Stable v0.2.4 uses @zamery/browser-provider@0.2.3, @zamery/browser-firefox@0.2.3, @zamery/browser-mcp@0.1.2, and @zamery/pi-browser@0.2.2, plus Mozilla-signed/public Firefox companion 0.2.6. Signed real-profile behavior and clean published-artifact acceptance both pass. See the release status for exact evidence.
Browser automation often hides important distinctions: whether the browser is user-owned, whether an action really happened, whether a DOM reference is still fresh, or whether a timeout occurred before or after mutation began. Zamery Browser keeps those boundaries explicit.
completed, not_started, partial, or unknown outcomes instead of converting ambiguity into success.The Firefox path uses a Mozilla-signed Zamery Browser Companion plus a Native Messaging host. Current signed companion 0.2.6 uses protocol 2. Protocol-1 0.1.x components remain incompatible and fail closed when mixed with protocol-2 components. See Firefox setup.
The npm packages are public under the @zamery scope and licensed under Apache-2.0. The API is still 0.x: additive work can land in minor releases, while intentional breaking changes are documented with migration notes rather than silently reinterpreting an existing protocol version.
Apache-2.0. Each package includes its own license file; the repository root license applies to the repository as a whole.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @zamery/browser-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-maemreyo-zamery-browser": {
"command": "npx",
"args": [
"-y",
"@zamery/browser-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@zamery/browser-mcpnpmZamery Browser works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.