anchor-browser

name

anchor-browser

description

Anchor Browser is a cloud-hosted automation platform that lets AI agents interact with web pages like a human—navigating sites, clicking, typing, submitting forms and extracting data—so teams can automate workflows where APIs are unavailable or limited. Read and write Anchor Browser data through One: sessions, tasks, identities, applications, extensions, profiles and more, 84 actions with real parameter documentation. Use whenever the user asks to look something up in Anchor Browser, create or update a record there, or build code against the Anchor Browser API.

Anchor Browser through One

Anchor Browser is a cloud-hosted automation platform that lets AI agents interact with web pages like a human—navigating sites, clicking, typing, submitting forms and extracting data—so teams can automate workflows where APIs are unavailable or limited.

One exposes Anchor Browser through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

1. Find the action in the table below, or call search_one_platform_actions with platform anchor-browser if it is not listed.
2. Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
3. Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm Anchor Browser is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.

Each connection carries an field. If it reports the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.