MCP Fetch
Related Servers
Alternatives to MCP Fetch
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseNot gradedqualityDmaintenanceAn 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.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for headless browser automation using Puppeteer, enabling AI to navigate, click, fill forms, take screenshots, and execute JavaScript on web pages.-
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to control and inspect a live Chrome browser via MCP, including performance tracing, network and console debugging, screenshots, and reliable Puppeteer-based automation.3,138,727 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables 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 npm1MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.