Skip to main content
Glama

Related Servers

Alternatives to MCP Fetch

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote browser automation via MCP, allowing models to open pages, read snapshots, click, fill, and select elements using Playwright, with built-in security restrictions against sensitive actions.
      -
    • 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
    • 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.
      -
    • 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
      Enables interaction with Chromium browser instances through Puppeteer for inspecting dev builds, capturing screenshots, and automating UI interactions. Features permission-gated tools for secure browser navigation, DOM manipulation, and JavaScript evaluation.
      6 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: fetch for HTTP requests, get-rules for documentation, graphql for GraphQL operations, puppeteer for browser automation, and socket for WebSocket management. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency3/5

    The naming conventions are mixed: fetch, graphql, and socket use lowercase single words, while get-rules uses kebab-case and puppeteer is a proper noun. This inconsistency reduces predictability, though the names remain readable and descriptive of their functions.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a utility-focused domain like web and browser operations. Each tool serves a distinct and essential purpose, such as HTTP requests, GraphQL, browser control, WebSocket management, and documentation, making the count appropriate and efficient.

    Completeness4/5

    The tool set covers key areas for web and browser automation, including HTTP, GraphQL, WebSockets, and Puppeteer, with a documentation tool for guidance. Minor gaps might exist, such as advanced caching or proxy handling, but core workflows are well-supported without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive