Skip to main content
Glama
README.md
# Browsa SDKs and MCP server

Official clients for [Browsa](https://browsa.io), cloud browsers for AI agents. Each browser is Phantom, Browsa's own Chromium build.

[![PyPI](https://img.shields.io/pypi/v/browsa?label=PyPI%20browsa)](https://pypi.org/project/browsa/)
[![npm browsa](https://img.shields.io/npm/v/browsa?label=npm%20browsa)](https://www.npmjs.com/package/browsa)
[![npm @browsa/mcp](https://img.shields.io/npm/v/@browsa/mcp?label=npm%20%40browsa%2Fmcp)](https://www.npmjs.com/package/@browsa/mcp)

| Package | Install | Published at | Source |
|---|---|---|---|
| Python SDK | `pip install browsa` | [PyPI: browsa](https://pypi.org/project/browsa/) | [`browsa-python`](browsa-python) |
| TypeScript SDK | `npm i browsa` | [npm: browsa](https://www.npmjs.com/package/browsa) | [`browsa-ts`](browsa-ts) |
| MCP server for Claude, Cursor and other MCP clients | `npx -y @browsa/mcp` | [npm: @browsa/mcp](https://www.npmjs.com/package/@browsa/mcp) | [`browsa-mcp`](browsa-mcp) |

## What you can do

- **Run an agent task.** Describe the job in plain language and get JSON back. Use your own Anthropic, OpenAI or Google key, or a hosted tier (`"llm": "browsa"`) with no key.
- **Drive a browser yourself.** Start a cloud Chromium and connect Playwright or Puppeteer over CDP.
- **Scrape, extract or screenshot a page** in one call.
- **Schedule a task and receive results** on a signed webhook.

```python
from browsa import Client

c = Client(api_key="agt_live_...")
job = c.run_task(task="Return the top 3 Hacker News stories as JSON", llm="browsa")
print(job.final_result)
```

```ts
import { Client } from "browsa";

const c = new Client({ apiKey: "agt_live_..." });
const job = await c.runTask({ task: "Return the top 3 Hacker News stories as JSON", llm: "browsa" });
console.log(job.finalResult);
```

New accounts get 100 free credits after email verification: no card, and credits never expire. Browsa does not supply proxies; you can bring your own HTTP, HTTPS or SOCKS5 proxy per browser.

## Links

- Website: https://browsa.io
- API docs: https://browsa.io/docs
- MCP setup guide: https://browsa.io/guides/mcp-server
- Pricing: https://browsa.io/pricing
- Status: https://browsa.io/status
- Support: support@browsa.io

## Issues

Bug reports and questions about the SDKs are welcome as GitHub issues in this repository. For account or billing questions, email support@browsa.io.

## License

MIT. See each package's `LICENSE` file.

TDQS

A3.7/5.0

Scored across 20 tools

Disambiguation4/5

The surface is split into clearly distinct clusters (managed jobs, self-driven browsers, identities, webhooks, schedules, billing), and descriptions explicitly contrast run_task vs start_browser and get_job vs list_job_files. Minor overlap remains between list_identities and list_browsers, and between create_schedule and run_task, but the descriptions resolve the boundaries well.

Naming Consistency4/5

Most names follow a clean snake_case verb_noun pattern (get_job, run_task, cancel_job, list_webhooks, create_webhook, delete_webhook, start_browser, stop_browser). A few outliers break the pattern: bare verbs observe and act, plus the noun phrases credits and proxy_network.

Tool Count4/5

At 20 tools this sits at the upper edge, but each tool maps to a genuinely distinct capability across jobs, browsers, schedules, webhooks and account data. Nothing looks duplicated or padded, though a couple of read-only helpers (list_models, credits, proxy_network) could plausibly be consolidated.

Completeness3/5

Core job lifecycle is well covered (run, poll, cancel, respond, list files) and browsers have start/stop/list. However there are real gaps: no tool to fetch the contents of files returned by list_job_files, no delete/get/update for schedules (only create and list), and webhooks lack a get/update operation.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues