otherapi_key

BrowserAct

BrowserAct runs hosted browser-automation workflows and exposes task execution, workflow discovery, templates, and proxy-region APIs.

Verdict

BrowserAct runs browser automation workflows on your behalf — scraping pages, filling forms, clicking through multi-step flows — and reports back structured data or screenshots. When you @mention it in a Project, your team can launch pre-built templates (price monitoring, lead enrichment, competitor research) or trigger custom workflows you've already configured in BrowserAct's dashboard. Tasks run headless in the cloud with proxy rotation, so you're not blocked by rate limits or CAPTCHAs. The catch: you need an active BrowserAct subscription and API key, and complex workflows still require upfront setup outside Switchy.

Common use cases

  • Monitor competitor pricing across e-commerce sites
  • Enrich lead lists with LinkedIn profile data
  • Scrape job postings for market research
  • Automate form submissions for testing
  • Extract structured data from dynamic pages

Integration

Vendor
BrowserAct
Category
other
Auth
API_KEY
Tools
11
Composio slug
browseract

Tools

  • Cancel Task

    Immediately and permanently cancel a running BrowserAct task. The canceled run cannot be resumed or recovered. A task already in a terminal state is also treated as successfully canceled.

  • Get Task

    Return either a task's current status or its full progress, outputs, files, live-view details, and failure information.

  • Get Workflow

    Return a custom workflow's metadata and expected input parameter definitions before a run.

  • Get Workflow Template

    Return an official template's metadata and expected input parameter definitions before a run.

  • List Proxy Regions

    Return the supported proxy region names and codes for official template runs.

  • List Tasks

    Return one cursor-controlled page of workflow tasks, optionally filtered by status, workflow, name, or creation time.

  • List Workflows

    Return one cursor-controlled page of custom workflows in the connected workspace.

  • List Workflow Templates

    Search official BrowserAct workflow templates and return one cursor-controlled page of summaries.

  • Resume Task

    Resume a paused task from its current state. Finished, failed, and canceled tasks cannot be resumed. BrowserAct also treats an already-running task as a successful request.

  • Run Workflow

    Start a custom BrowserAct workflow. This consumes credits and executes its configured browser actions, which may irreversibly modify external websites.

  • Run Workflow Template

    Start an official BrowserAct workflow template. This consumes credits and executes its browser actions, which may cause irreversible effects on external websites.

Setup

Setup guide

  1. 11. Log in to your BrowserAct dashboard and navigate to Settings → API Keys. 2. Generate a new key with read and write permissions, then copy it to your clipboard. 3. In Switchy, open Settings → Integrations and click Connect next to BrowserAct. 4. Paste your API key into the prompt and click Authorize. 5. Switchy will verify the key by listing your workflows; if successful, you'll see a green checkmark. 6. Open any Project, type '@BrowserAct list my workflows' and send — you should see a table of custom workflows or templates. 7. To run a task, @mention BrowserAct again with a workflow name and any required inputs (URL, search term, etc.). 8. Poll task status by asking '@BrowserAct get task [task_id]' until it completes, then retrieve outputs or screenshots from the response.

What teammates see: by default, memories from BrowserAct are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

List Available Templates

@BrowserAct list all workflow templates and show me the top five by popularity, including what inputs each one expects.

Run Price Check

@BrowserAct run the 'Product Price Monitor' template for https://example.com/product/12345 using the US proxy region, then show me the extracted price and availability.

Check Task Progress

@BrowserAct get the status of task abc-123-def and tell me how many steps are done, what the current action is, and if there are any failures.

Enrich Contact List

@BrowserAct run my 'LinkedIn Lead Scraper' workflow with the input file contacts.csv, then return the enriched records as JSON when it finishes.

Cancel Long Task

@BrowserAct cancel task xyz-789-ghi immediately and confirm it's been terminated so I can start a corrected run.

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@BrowserAct list all my running tasks from the last 24 hours and show me which ones are taking longest

Output

Found 4 active tasks from the past day. Two are still running: 'competitor-pricing-scan' (started 3h ago, currently navigating page 47 of 120) and 'form-submission-test' (started 45m ago, waiting for CAPTCHA). One completed successfully ('daily-screenshot-batch', 2h runtime), and one failed ('login-flow-test', authentication timeout after 8 minutes). The pricing scan is your longest-running task and may benefit from pagination adjustments.

Notes

This example shows BrowserAct's task-monitoring capability. The List Tasks tool supports filtering by status and time range, but the response shape depends on how many tasks exist in your workspace. Tasks in 'running' state consume execution credits until completion or cancellation.

Prompt

@BrowserAact cancel the competitor-pricing-scan task immediately, it's stuck in a loop

Output

Task 'competitor-pricing-scan' (ID: task_abc123) has been canceled. The browser session terminated at page 47, and no further credits will be charged. Partial results captured before cancellation remain accessible via Get Task for the next 30 days. Note that canceled tasks cannot be resumed—you'll need to start a new run if you want to complete the workflow.

Notes

Demonstrates the Cancel Task action, which is permanent and immediate. Useful when a workflow hits an unexpected state or you need to stop credit consumption. The MCP requires the task ID (obtained from List Tasks or a previous run reference), and cancellation works even if the task is already failed or completed.

Prompt

@BrowserAct search the workflow templates for anything related to e-commerce product scraping, then explain which one would work best for a site with lazy-loaded images

Output

Found 3 relevant templates: 'E-commerce Product Catalog Scraper' (handles pagination and basic lazy-load via scroll triggers), 'Dynamic Content Extractor' (waits for network idle and DOM mutations, better for React/Vue apps), and 'Visual Product Grid Scraper' (screenshot-based, no DOM parsing). For lazy-loaded images, the Dynamic Content Extractor is your best fit—it monitors network requests and waits for image elements to populate before extraction. The Product Catalog template may miss images that load after initial scroll. Both require you to specify CSS selectors for the product containers.

Notes

This synthesis example pairs BrowserAct's template search with reasoning about technical requirements. The List Workflow Templates tool returns metadata and input parameters, but the AI must interpret which template matches the user's constraint. Template selection depends on the target site's architecture, which the MCP cannot inspect without a live run.

Use-case deep-dives

Competitive pricing scrape for e-commerce

When BrowserAct beats manual price checks at 10+ SKUs

A 6-person e-commerce team needs daily competitor pricing on 40 SKUs across three marketplaces. BrowserAct's workflow templates handle the scraping and proxy rotation, returning structured data the team can pipe into Sheets or a dashboard. The API_KEY auth means anyone on the team can trigger a run from Switchy without touching credentials. This works until you hit rate limits or need sub-hourly updates—at that scale, you're better off with a dedicated scraping service. The 11 tools give you task lifecycle control (cancel, status, list) and workflow discovery, so you can build a repeatable cadence without writing scraper code. If your pricing window is daily and your SKU count is under 200, BrowserAct keeps the workflow in one place and the data fresh.

Lead enrichment from public profiles

BrowserAct for sales teams running outbound at 50-100 leads per week

A 3-person sales team pulls LinkedIn and company-site data for 60 leads each week before cold outreach. BrowserAct's workflow templates automate the profile visits and data extraction, returning contact details and recent activity in a structured format. The Get Task and List Tasks tools let the team monitor progress in Switchy and retry failures without leaving the workspace. This setup breaks down if you need real-time enrichment during a call or if your lead volume spikes past 500 per week—then you want a dedicated enrichment API with sub-second latency. The proxy region support (List Proxy Regions) helps avoid blocks when scraping at volume. If your outbound motion is weekly batches and you're under 200 leads, BrowserAct keeps enrichment simple and the data in one shared context.

Compliance screenshot archive for regulated content

When BrowserAct handles quarterly audit trails for small compliance teams

A 4-person compliance team at a fintech needs timestamped screenshots of 30 public-facing pages every quarter for SOC 2 evidence. BrowserAct's workflow templates capture the pages, store the files, and return metadata the team can attach to audit reports. The Get Task tool surfaces live-view details and file outputs directly in Switchy, so the team doesn't juggle storage buckets. This works for quarterly or monthly cadences; if you need daily snapshots or version-diffing, you'll want a dedicated monitoring tool with alerting. The Cancel Task and List Tasks tools give you recovery options when a run hits a timeout or a page layout changes mid-capture. If your audit frequency is quarterly and your page count is under 100, BrowserAct keeps the evidence collection repeatable without custom infrastructure.

Frequently asked

What does the BrowserAct MCP do in Switchy?

It lets your AI agents launch and control browser automation workflows through BrowserAct's API. You can start tasks, check their status, retrieve outputs and files, and cancel running jobs. The MCP exposes both official BrowserAct templates and any custom workflows you've built in your BrowserAct workspace, so agents can trigger web scraping, form filling, or multi-step browser interactions without writing Playwright code.

Do I need a BrowserAct API key to connect this MCP?

Yes. The MCP uses API key authentication, so you'll need to generate one from your BrowserAct account settings before connecting it in Switchy. The key grants access to all workflows in the associated BrowserAct workspace. Anyone on your Switchy team who connects the MCP will need their own key, or you can share a single workspace key if your BrowserAct plan allows it.

Can the MCP edit or create new BrowserAct workflows?

No. It can only list existing custom workflows and official templates, then run them. If you need to change a workflow's steps or build a new one, you still do that in the BrowserAct dashboard. The MCP is read-and-execute: agents can see what workflows are available, kick them off with parameters, and fetch results, but they can't modify workflow definitions.

Why use this MCP instead of calling BrowserAct's API directly?

The MCP wraps BrowserAct's REST endpoints so your AI agents can discover workflows, read parameter schemas, and handle pagination without you writing HTTP boilerplate. If you're already comfortable with BrowserAct's API and want full control over error handling or streaming logs, stick with direct calls. The MCP trades flexibility for convenience: agents get structured tool descriptions and Switchy handles credential injection.

Who on the team should connect the BrowserAct MCP?

Whoever owns your BrowserAct workspace and can generate API keys. If multiple people need to trigger workflows from Switchy, either share one connection or have each person connect their own BrowserAct account. Running tasks through the MCP counts against your BrowserAct plan's execution limits, not Switchy's, so coordinate with whoever manages that quota.

More other MCPs

See all other MCPs →

Data last verified 61 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.