Skip to main content
Glama
bytesbrains

mcp-textbrowser

by bytesbrains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-textbrowser

No user-submitted related servers found.

    Related Servers

    • krwl3r

      garciarsdiego
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.
      1
      MIT

    • MCP Master Puppeteer

      flrngel
      F
      license
      Not graded
      quality
      D
      maintenance
      An advanced MCP server for browser automation using Puppeteer, specifically optimized for token efficiency through minimal data returns and progressive enhancement. It enables agents to navigate pages, capture LLM-optimized screenshots, extract structured content, and perform batch interactions.
      3
      -
    • Plasmate by plasmate-labs

      Plasmateofficial

      plasmate-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Agent-native headless browser for AI agents. Converts web pages to a Semantic Object Model (SOM) instead of raw HTML — 17x average token reduction across real-world sites (up to 117x on complex pages). Native MCP server with fetch_page, extract_text, extract_links, and full browser automation. No API key required.
      28 npm
      Apache 2.0

    • Fetch Browser

      TheSethRose
      A
      license
      B
      quality
      F
      maintenance
      A headless browser MCP server that allows AI agents to fetch web content and perform Google searches without API keys, supporting various output formats like Markdown, JSON, HTML, and text.
      2
      24
      MIT

    • mcp-page-capture

      chasesaurabh
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that uses headless Chromium (Puppeteer) to capture pixel-perfect screenshots and extract DOM from URLs, with LLM-friendly step-based workflows.
      2
      10 npm
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct browser action (navigate, click, type, scroll, read, screenshot, evaluate) with no overlap in purpose.

    Naming Consistency5/5

    All tool names follow the consistent 'browser_verb' pattern, making the set predictable and easy to understand.

    Tool Count5/5

    7 tools is well-scoped for a browser automation server, covering essential interactions without being excessive or insufficient.

    Completeness4/5

    Covers core browsing actions well, but lacks explicit back/forward navigation or page refresh, which are minor gaps for typical workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources