Anchor Browser MCP integration for AI agents.
Connect AI agents to Anchor Browser through 3 structured actions, including get billing info, start browser session, and get project metadata. Review authent…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Anchor Browser integration exposes
The Anchor Browser Agent App exposes 3 provider-backed actions for developer tools and ai work. Its current contract lets an authorized agent retrieve anchor browser project billing balance, usage, tier, and browser limits, start an anchor browser session and return its cdp and live-view connection urls, and retrieve lightweight anchor browser project metadata by project id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Anchor Browser account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Anchor Browser capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_billing_infoREADRetrieve Anchor Browser project billing balance, usage, tier, and browser limits.
start_browser_sessionWRITEStart an Anchor Browser session and return its CDP and live-view connection URLs.
INPUTS: session / browser / integrations / identities
get_project_metadataREADRetrieve lightweight Anchor Browser project metadata by project ID.
INPUTS: projectId
INPUT CONTRACTS
Know what the action needs before it runs.
start_browser_session
sessionOPTIONAL- Session-related configuration sent to Anchor Browser.
browserOPTIONAL- Browser-specific configuration sent to Anchor Browser.
integrationsOPTIONAL- Integrations to load in the browser session.
identitiesOPTIONAL- Authenticated identities to activate in the session.
get_project_metadata
projectIdOPTIONAL- The Anchor Browser project ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Billing Info
Retrieve Anchor Browser project billing balance, usage, tier, and browser limits. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_billing_infoControl Start Browser Session
Start an Anchor Browser session and return its CDP and live-view connection URLs. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
start_browser_sessionVerify with Get Project Metadata
Retrieve lightweight Anchor Browser project metadata by project ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_project_metadataSAFETY BOUNDARY
Operate Anchor Browser with explicit limits
- Authorize Anchor Browser with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Anchor Browser rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Anchor Browser task completed successfully.
CONNECTION MODEL
API key
Anchor Browser API key sent in the anchor-api-key header. Create or manage API keys in Anchor project settings: https://app.anchorbrowser.io/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Anchor Browser.