Skip to main content
Glama
Fetcher MCP

Fetcher MCP

πŸš€ Fetcher MCP - Playwright Headless Browser Server

Welcome to the Fetcher MCP GitHub repository! This repository hosts the MCP server for fetching web page content using the Playwright headless browser.

🧠 About

The Fetcher MCP is designed to leverage artificial intelligence capabilities to efficiently retrieve web page content. By utilizing the Playwright headless browser, this server can navigate through web pages and extract desired information with ease.

Related MCP server: Fetch MCP

🎯 Key Features

πŸ€– AI-Powered Content Fetching
πŸ”— Playwright Integration
πŸš€ Fast and Efficient
🌟 Easy Setup and Configuration

πŸ“š Repository Details

  • Name: fetcher-mcp

  • Description: MCP server for fetch web page content using Playwright headless browser

  • Topics: AI, MCP, Playwright

πŸ“¦ Latest Release

You can download the latest version of the Fetcher MCP server from the following link:
Download Fetcher MCP

:information_source: Note:

The provided link leads directly to the application file. Please make sure to launch the application after downloading.

If the link is not accessible or does not work, you can check the "Releases" section of this repository for alternative download options.

πŸš€ Get Started

To start using the Fetcher MCP server for content fetching, follow these simple steps:

  1. Download the latest version from the link above.

  2. Unzip the downloaded file to your desired location.

  3. Launch the application.

  4. Configure the server settings as needed.

  5. Start fetching web page content effortlessly!

🌐 Additional Resources

For more information, resources, or support regarding the Fetcher MCP server, feel free to visit the official website at https://github.com/everford/fetcher-mcp/releases.

πŸ“ Contribution Guidelines

We welcome contributions to enhance the Fetcher MCP server and make it even more powerful and efficient. If you have any ideas, suggestions, or improvements, please submit a pull request following our guidelines.

πŸ™Œ Join Our Community

Connect with other developers, share insights, and stay updated on the latest news related to the Fetcher MCP server by joining our community:

πŸ‘₯ Slack Channel
🐦 Twitter
πŸ“§ Newsletter


πŸš€ Start using the Fetcher MCP server today for seamless web page content fetching with AI-powered capabilities. Effortlessly extract the information you need using the Playwright headless browser integration. Happy Fetching! 🌟


Remember, the Fetcher MCP server simplifies the process of web page content retrieval, making it faster and more efficient than ever before. Download the latest version now and experience the power of AI and Playwright in action. Happy fetching! πŸš€

Available Tools

2 tools
fetch_urlC

Retrieve web page content from a specified URL

Inputs: url (required), debug, disableMedia, extractContent, +6 more.

fetch_urlsC

Retrieve web page content from multiple specified URLs

Inputs: urls (required), debug, disableMedia, extractContent, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 2 tools

    Disambiguation3/5

    The two tools have overlapping purposesβ€”both fetch web page contentβ€”but the descriptions clarify that one handles a single URL while the other handles multiple URLs. This distinction is clear enough to avoid misselection, but the core functionality is identical, leading to some ambiguity in why they are separate tools.

    Naming Consistency5/5

    The tool names follow a perfectly consistent verb_noun pattern with 'fetch_url' and 'fetch_urls', using snake_case throughout. The naming is predictable and clear, with no deviations in style or convention.

    Tool Count2/5

    With only two tools, the server feels under-scoped for a general-purpose 'Fetcher' domain. A single tool with parameters for single or multiple URLs could suffice, making the current count seem redundant and inefficient for typical agent workflows.

    Completeness2/5

    The tool surface is severely incomplete for web fetching; it lacks essential operations like handling HTTP methods (e.g., POST), managing headers, parsing content, or error handling. Agents will face dead ends when needing more than basic retrieval, causing frequent failures.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      An advanced web browsing server enabling headless browser interactions via a secure API, providing features like navigation, content extraction, element interaction, and screenshot capture.
      6
      27
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      An MCP server that retrieves web page content using Playwright headless browser, capable of extracting main content and converting to Markdown format.
      3
      5,605 npm
      1,088
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A browser automation server providing Playwright capabilities for controlling web browsers, capturing screenshots, extracting content, and performing complex interactions through an MCP interface.
      6
      Apache 2.0