Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BROWSA_API_KEYNoBrowsa API key (agt_live_...). Mint one at https://app.browsa.io/dashboard/keys

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
run_taskA

Run a browser-driven AI task on a fresh real Chromium burner. Returns the final result, the outcome and the total steps. status: completed only means the run ended: read outcome. outcome: failed with status: completed means the agent finished but could not do the task, and final_result says what stopped it. Use this when the user asks for anything web-shaped: scrape, fill, click, extract, login, place an order, search, summarize a page, etc. The browser is a real macOS-Chrome-fingerprinted Chromium with built-in CAPTCHA solving (Turnstile, hCaptcha, reCAPTCHA, ALTCHA, FunCaptcha) and behavioral humanization. Default timeout: 10 minutes.

get_jobA

Fetch the current state of a previously-submitted job by UUID. Returns status (queued|running|completed|failed|input_required; a cancelled job is failed with error_code CANCELLED), step count, final_result text if terminal, and the live_url of the browser's live view while it runs. Cheap — call repeatedly to poll a long-running job started by run_task.

cancel_jobA

Cancel a queued or running job. The job ends as failed with error_code CANCELLED and keeps its browser charge. A job that already finished returns an error with code JOB_NOT_CANCELLABLE.

respond_to_jobA

Answer an input_required prompt (CAPTCHA solution, human decision point). Flips the job back to running.

start_browserA

Start a real cloud browser and return its CDP URL, so you can drive it yourself with Playwright or Puppeteer (connect_over_cdp) instead of handing the work to run_task. Use this when you want to write the browser steps, or need the page open across several of your own tool calls. Billed per browser; always call stop_browser when you are done. Without a proxy the browser uses Browsa's data-center IP.

proxy_networkA

Say whether Browsa's built-in proxy network is enabled on this server and, when it is, list its tiers (datacenter, residential) with the exit countries of each and the price per GB in credits. Call this before passing proxy {"network": ...} to start_browser. When enabled is false, only your own proxy can be used.

stop_browserA

Stop a browser started with start_browser and release it. Always call this when finished; an unused browser keeps running until its ttl expires.

observeA

Read the page of a browser started with start_browser, as compact text: one line per element, [id] role "name" state, inside a token budget. Use the ids with the act tool. No Playwright or CDP needed, and no extra charge. Ids stay valid across observe and act calls until the page loads a new document. On a full-page bot check nothing is read and the first lines say so.

actA

Perform one action in a browser started with start_browser and get back what changed (~ changed, + added, - removed), or a new view after a navigation. Input is sent as real mouse and key events. Name the element by id from observe, or by role and name, or click a point with x and y. The first line of the answer says failed, blocked, challenge or stale when the action did not go through. stale: the ids are from a view that no longer exists, nothing was done, and a new view follows.

list_browsersA

List this workspace's browsers (burners and saved identities) with their status.

creditsA

Get the current credit balance + available top-up packs.

list_webhooksA

List webhook subscriptions for this workspace.

create_webhookA

Register a callback URL the platform will POST lifecycle events to (HMAC-SHA256 signed via X-Agents-Signature). Use the verify helper from browsa/webhooks in your receiver.

delete_webhookB

Delete (disable) a webhook subscription by id.

list_identitiesA

List persistent browser identities (long-lived cookies/history/fingerprint, billed monthly). Use one in run_task via profile_id to reuse a warmed-up session — critical for sites that fingerprint cookie age, session continuity, or behavioral history (Akamai, Cloudflare-strict, DataDome).

create_scheduleA

Schedule a browser task to run automatically on a fixed interval (min 1 hour). Each run is a normal billed task. LLM key: same rules as run_task (the workspace's default saved key unless llm_key_id is given); the schedule stores only the saved key's id. With no llm and no saved key, the schedule runs on Browsa's hosted model and the result says so. Pass llm "browsa", "browsa-fast" or "browsa-smart" to choose a hosted tier.

list_schedulesA

List this workspace's scheduled tasks (id, task, interval, next run, run count). Secrets redacted.

list_llm_keysA

List the LLM provider keys saved in this workspace: id, name, provider, masked key (prefix + last 4), whether it is the default for its provider, and its status (valid, invalid or unchecked). Never returns a secret. Pass an id as llm_key_id to run_task or create_schedule. Keys are added at https://app.browsa.io/dashboard/llm-keys.

list_modelsA

List the hosted tiers (browsa, browsa-fast, browsa-smart: the model each runs on, its default reasoning and credits per task) and the providers a saved or per-task LLM key can be for. Read-only and free.

list_job_filesA

List the output files a task wrote — extracted data + a session.gif recording. Returns name + size per file.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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