Skip to main content
Glama
rsi-ai-platform

browser-research-mcp

Related Servers

Alternatives to browser-research-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation and web scraping by exposing Playwright tools through an HTTP-based MCP server. Users can navigate pages, interact with web elements, capture screenshots, and extract structured content using a persistent Chromium instance.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI-powered browser automation, web scraping, and testing using Playwright across Chromium, Firefox, and WebKit. It allows users to perform actions like navigation, clicking, typing, and taking screenshots through natural language interfaces.
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for browser automation using Puppeteer that enables AI assistants to navigate web pages, interact with UI elements, and capture screenshots. It supports comprehensive web tasks including form filling, content extraction, and executing custom JavaScript within the browser context.
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server that provides browser automation capabilities through a Chrome extension, enabling terminal-based agents to interact with any website via a live browser session with optimized context.
      1
      42 npm
      3
      Apache 2.0
    • A
      license
      C
      quality
      C
      maintenance
      Provides browser automation and web scraping as MCP tools, enabling autonomous URL ingestion, crawling, extraction, and anti-bot handling with interactive browser control.
      62
      5
      MIT

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: 'visit' fetches raw page state, 'extract' performs structured extraction on a static page, and 'act' handles interactive flows with extraction. The descriptions explicitly highlight when to use each, leaving no ambiguity.

    Naming Consistency5/5

    All tool names are single imperative verbs ('act', 'extract', 'visit'), following a consistent pattern. While not verb_noun compound names, the style is uniform and predictable.

    Tool Count5/5

    With only 3 tools, the server covers the essential browser automation tasks: raw page access, static extraction, and interactive extraction. The count is well-scoped and avoids unnecessary bloat.

    Completeness4/5

    The tool set covers the core workflows (fetch, extract, interact+extract). A minor gap is the lack of a standalone interaction tool without extraction, but this can be approximated via 'act' with a trivial focus. Overall, the surface feels reasonably complete for browser research.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing