Skip to main content
Glama
gzigurella

chromium-mcp

by gzigurella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to chromium-mcp

No user-submitted related servers found.

    Related Servers

    • scribe-me

      jlehman
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server to scrape web pages to clean Markdown via headless Chromium, with support for single or batch URLs.
      -

    • fetch-rendered-page-mcp

      blono
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that fetches and renders dynamic web pages (SPA) using Chromium, returning content as Markdown or text. It uses lightweight HTTP first with automatic fallback to a browser for JS-heavy sites, and includes SSRF protection, login session support, and batch fetching.
      -

    • Shark-no-Kari

      HaiNick
      A
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP server for web scraping with anti-bot evasion. Provides stealth HTTP fetching, headless browser with Cloudflare bypass, CSS selectors, YouTube transcripts, and Markdown conversion.
      1
      MIT

    • pulldown

      anthony-maio
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for retrieving web pages as clean Markdown, with configurable detail levels and optional Chromium rendering for JavaScript-heavy pages.
      1
      MIT

    • puppeteer

      silvino-av
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for headless browser automation using Puppeteer, enabling AI to navigate, click, fill forms, take screenshots, and execute JavaScript on web pages.
      -
    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/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: fetching full page, extracting data via selectors, getting link info, interacting with elements, and taking screenshots. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., fetch_page, extract_data, get_link, interact, screenshot). No mixing of conventions.

    Tool Count5/5

    5 tools is well-scoped for a browser automation server, covering the essential workflows without being excessive or insufficient.

    Completeness4/5

    The tool set covers core web scraping needs: fetching, extracting, interacting, and screenshots. Minor gaps exist (e.g., cookie handling, network capture), but the surface is largely complete for common use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources