Integration
Connect Anchor to Browserbase
When New Proposal Sent fires in Anchor, your agent runs Fetch page in Browserbase. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Anchor and Browserbase to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Anchor can start in Browserbase
When New Proposal Sent in Anchor
then Fetch page in Browserbase
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Anchor and Browserbase
Triggers and actions 4 triggers · 18 actions
- Agreement Amended
Triggers when an agreement is amended.
- New Proposal Sent
Triggers when a proposal is sent to a client.
- Proposal Approved
Triggers when a proposal is approved. The payload is the resulting agreement (a proposal becomes an agreement on approval).
- Proposal Published
Triggers when a proposal is published.
- Add Service to Agreement
Adds a service to a signed Anchor agreement as a new amendment.
- Create Contact
Creates a new client contact in Anchor.
- Find Contact by ID
Looks up a single contact by its Anchor ID.
- List Contacts
Returns a list of contacts (client businesses), optionally filtered by search text or status.
- Publish Proposal
Publishes a proposal draft as a proposal and, unless set to silent, emails the client.
- Submit Charges
Submits charges on an agreement to issue an invoice now or schedule one for a future billing date.
- Add context
Creates a new browser Context that persists cookies and storage across Browserbase sessions.
- Add session
Creates a new Browserbase browser session and returns its id along with the URLs used to connect to it.
- Delete context
Deletes a browser context (saved cookies and browser state) from your Browserbase project.
- Fetch page
Fetches a web page through Browserbase and returns its content (raw, markdown, or schema-extracted JSON), status code and headers.
- Get context
Returns a Browserbase context (saved browser state) by its id, including its name, project and timestamps.
- Get run
Returns the current status and details of an agent run, including its result and the browser session it used.
- Get session
Returns a Browserbase browser session, including its status, region, timestamps and connection URLs.
- List downloads
Returns the files downloaded during a Browserbase session, optionally filtered by filename, MIME type, size or creation time.
- List sessions
Returns the browser sessions in your Browserbase project, optionally filtered by status or by user metadata.
- Run agent
Starts a Browserbase browser agent run that completes a natural-language task using web search and browser tools. Returns the new run, which starts in a pending state.
- Search web
Runs a web search through Browserbase and returns the matching pages with their titles and URLs.
- Update session
Updates a Browserbase session, such as requesting that it be released before its timeout to stop further charges.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Anchor
Anchor to OutlookOutlook is Microsoft's email and calendaring platform integrating contacts and scheduling, enabling users to...
Anchor to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Anchor to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Anchor to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Anchor to Google SheetsGoogle Sheets
Anchor to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Browserbase
Google Calendar to BrowserbaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Anchor and Browserbase, answered
What can start an automation from Anchor?
Any of Anchor's 4 triggers in the catalog, including New Proposal Sent, Agreement Amended, Proposal Approved and Proposal Published. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Browserbase when something happens in Anchor?
Any of Browserbase's 12 actions, including Update session, Add context, Add session and Fetch page. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Browserbase to Anchor?
Browserbase has no triggers in the catalog today, so automations start in Anchor. If you need the other direction, ask: your agent reads Browserbase's API documentation and adds it.
Do I have to build a connector for Anchor or Browserbase?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.