Skip to main content
Glama
enesjakozh
JeremyNixon

MCP Fetch

by JeremyNixon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Obtención de MCP

insignia de herrería

Servidor de Protocolo de Contexto de Modelo para obtener contenido web y procesar imágenes. Esto permite a Claude Desktop (o a cualquier cliente MCP) obtener contenido web y gestionar imágenes correctamente.

Inicio rápido (para usuarios)

Para utilizar esta herramienta con Claude Desktop, simplemente agregue lo siguiente a su configuración de Claude Desktop ( ~/Library/Application Support/Claude/claude_desktop_config.json ):

{
  "tools": {
    "fetch": {
      "command": "npx",
      "args": ["-y", "@kazuph/mcp-fetch"]
    }
  }
}

Esto descargará y ejecutará automáticamente la última versión de la herramienta cuando sea necesario.

Configuración requerida

  1. Habilitar accesibilidad para Claude:

    • Abrir configuración del sistema

    • Vaya a Privacidad y seguridad > Accesibilidad

    • Haga clic en el botón "+"

    • Añade a Claude desde tu carpeta de Aplicaciones

    • Encienda el interruptor para Claude

Esta configuración de accesibilidad es necesaria para que las operaciones automatizadas del portapapeles (Cmd+V) funcionen correctamente.

Related MCP server: @kazuph/mcp-fetch

Para desarrolladores

Las siguientes secciones son para aquellos que quieran desarrollar o modificar la herramienta.

Prerrequisitos

  • Node.js 18+

  • macOS (para operaciones del portapapeles)

  • Claude Desktop (instalación desde https://claude.ai/desktop )

  • tsx (instalación mediante npm install -g tsx )

Instalación

Instalación mediante herrería

Para instalar MCP Fetch para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install @kazuph/mcp-fetch --client claude

Instalación manual

git clone https://github.com/kazuph/mcp-fetch.git
cd mcp-fetch
npm install
npm run build

Especificaciones de procesamiento de imágenes

Al procesar imágenes de contenido web, se aplican los siguientes límites:

  • Máximo 6 imágenes por grupo

  • Altura máxima de 8000 píxeles por grupo

  • Tamaño máximo de 30 MB por grupo

Si el contenido excede estos límites, las imágenes se dividirán automáticamente en varios grupos y tendrás que pegarlas (Cmd+V) varias veces.

Configuración

  1. Asegúrese de que Claude Desktop esté instalado y funcionando.

  2. Instale tsx globalmente si aún no lo ha hecho:

npm install -g tsx
# or
pnpm add -g tsx

  1. Modifique la configuración de Claude Desktop ubicada en: ~/Library/Application Support/Claude/claude_desktop_config.json

Puedes encontrarlo fácilmente a través del menú de Claude Desktop:

  1. Abra Claude Desktop

  2. Haga clic en Claude en la barra de menú de Mac

  3. Haga clic en "Configuración"

  4. Haga clic en "Desarrollador"

Agregue lo siguiente a la configuración de su cliente MCP:

{
  "tools": {
    "fetch": {
      "args": ["tsx", "/path/to/mcp-fetch/index.ts"]
    }
  }
}

Herramientas disponibles

  • fetch : recupera URLs de internet y extrae su contenido como Markdown. Las imágenes se procesan y preparan automáticamente para las operaciones del portapapeles.

Notas

  • Esta herramienta está diseñada solo para macOS debido a su dependencia de las operaciones del portapapeles específicas de macOS.

  • Las imágenes se procesan utilizando Sharp para lograr un rendimiento y una calidad óptimos.

  • Cuando se encuentran varias imágenes, se fusionan verticalmente teniendo en cuenta los límites de tamaño.

  • Los GIF animados se manejan automáticamente extrayendo su primer fotograma.

Available Tools

1 tool
fetchA

Retrieves URLs from the Internet and extracts their content as markdown. If images are found, they are merged vertically (max 6 images per group, max height 8000px, max size 30MB per group) and copied to the clipboard of the user's host machine. You will need to paste (Cmd+V) to insert the images.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
maxLengthNo
startIndexNo
rawNo

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: content extraction to markdown, image merging with specific limits (max 6 images, max height 8000px, max size 30MB), and clipboard copying with a manual paste requirement. However, it omits details like error handling, rate limits, or authentication needs, leaving some gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the core functionality. Every sentence adds value: the first covers retrieval and extraction, the second details image handling, and the third provides a usage note. It could be slightly more concise by integrating the image limits into one sentence, but overall it's efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (image processing, clipboard operations) and no annotations or output schema, the description is partially complete. It covers the main behaviors but lacks details on return values, error cases, or parameter effects. For a tool with 4 parameters and significant functionality, more context would be beneficial to fully guide an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'URLs' (plural) but only one 'url' parameter is required, and it does not explain the semantics of 'maxLength', 'startIndex', or 'raw'. The description adds no meaning beyond the schema, failing to address the coverage gap adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('retrieves URLs', 'extracts content as markdown') and resources ('URLs from the Internet'). It distinguishes itself by detailing the unique image handling behavior (merging, copying to clipboard), which is not implied by the name alone. No siblings exist to differentiate from, but the description is comprehensive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for fetching and processing web content with images, but provides no explicit guidance on when to use this tool versus alternatives (e.g., other fetch tools or methods). It mentions a prerequisite ('You will need to paste...') but lacks context on exclusions or comparisons. With no sibling tools, this is adequate but not optimal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool update
    • First observedfetch
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

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The single tool 'fetch' has a clear and distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The name 'fetch' follows a simple verb pattern, which is appropriate for its function, and there is no inconsistency in naming conventions.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. For a server named 'MCP Fetch', which suggests fetching-related operations, having only one tool feels thin and insufficient for covering potential variations or related tasks in the domain.

Completeness2/5

The server's domain appears to be fetching and processing web content, but with only one tool, there are significant gaps in coverage. For example, there are no tools for handling different fetch methods, error handling, caching, or other related operations, which could lead to agent failures when more complex fetching scenarios arise.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches