@ainative/browser-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AINATIVE_API_KEY | No | API key for AINative Cloud. Get from https://ainative.studio/dashboard. | |
| AINATIVE_PASSWORD | No | Password for AINative Cloud authentication. | |
| AINATIVE_USERNAME | No | Username for AINative Cloud authentication. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_actA | Perform an action on a web page using AI-powered browser automation. Use when you need to click, type, navigate, or otherwise interact with a page. (50 credits) |
| browser_extractA | Extract structured data from a web page. Use when you need to scrape, parse, or retrieve specific information from a URL. Returns data in structured JSON format. (75 credits) |
| browser_validateA | Validate content or state on a web page. Use when you need to assert that specific content exists, a form was submitted, or a page reached an expected state. (25 credits) |
| browser_taskA | Run a multi-step browser automation task. Use when you need to perform a complex, multi-step workflow on a web page (e.g. login and fill out a form). More capable than browser_act for complex flows. (200 credits) |
| browser_extract_to_tableA | Extract structured data from a web page and store it directly in a ZeroDB NoSQL table. Use when you need to scrape data and persist it for later querying or analysis. (100 credits) |
| browser_enrich_memoryA | Extract content from a web page and store it in agent memory (ZeroDB). Use when you want an agent to "remember" information from a URL for future recall. (100 credits) |
| browser_batch_extractA | Extract structured data from up to 10 URLs in a single call and store rows in a ZeroDB table. Use when you need to scrape multiple pages at once. (75 credits per URL) |
| browser_enrich_memory_asyncA | Queue an async browser memory enrichment task. Returns a task_id immediately — the browser visits the URL and stores content in ZeroMemory in the background. (100 credits) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Several tools involve extracting data from a page (browser_extract, browser_extract_to_table, browser_batch_extract, browser_enrich_memory, browser_enrich_memory_async), and their differences (output format vs. storage destination) may not be immediately clear. Browser_act and browser_task also overlap in describing page interactions. Descriptions help, but boundaries are not perfectly distinct.
All tools share the 'browser_' prefix and are verb-oriented, giving a consistent feel. However, the structure varies: simple verbs (act, extract, validate), compound verbs (extract_to_table, enrich_memory), and an adjective+verb form (batch_extract). This minor inconsistency is still readable and predictable enough.
Eight tools is well within the ideal range and matches the server's purpose of browser automation. Each tool has a specific role in acting, extracting, validating, or persisting data, so the count feels appropriate without being excessive.
The toolset covers single interactions, complex multi-step workflows, extraction, validation, and persistent storage options, including batch and async variants. Minor gaps like explicit screenshot capture or session/cookie management exist, but the core browser automation lifecycle is well represented.