A
licenseNot graded
qualityD
maintenanceMCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.
1
MIT
@ainative/browser-mcp
OfficialRelated Servers
Alternatives to @ainative/browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server providing browser automation for AI agents with context-aware playbooks and skills for complex websites.7176PolyForm Noncommercial 1.0.0
- AlicenseBqualityDmaintenanceAn MCP server that provides browser automation capabilities, enabling LLMs to control a web browser for navigation, interaction, and data extraction.3214913MIT
- AlicenseAqualityBmaintenanceMCP server for AI browser automation with tools for navigation, actions, data extraction, and scripting, supporting local and cloud execution.141052Apache 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to automate browser testing via Chromium, providing tools for navigation, interaction, and inspection.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents real browser capabilities including screenshotting, action execution, data extraction, and multi-persona auditing for frontend validation.746MIT
TDQS
A3.9/5.0
Scored across 8 tools
Disambiguation3/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive