en es ja ko zh

@kazuph/mcp-fetch

Name: @kazuph/mcp-fetch
Author: kazuph

by kazuph

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

MCP 获取

用于获取 Web 内容和处理图像的模型上下文协议服务器。这使得 Claude Desktop（或任何 MCP 客户端）能够获取 Web 内容并进行适当的图像处理。

快速入门（针对用户）

要将此工具与 Claude Desktop 一起使用，只需将以下内容添加到您的 Claude Desktop 配置（ ~/Library/Application Support/Claude/claude_desktop_config.json ）中：

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

这将在需要时自动下载并运行该工具的最新版本。

所需设置

为 Claude 启用辅助功能：
- 打开系统设置
- 前往“隐私和安全”>“辅助功能”
- 点击“+”按钮
- 从您的应用程序文件夹添加 Claude
- 为克劳德打开开关

自动剪贴板操作（Cmd+V）需要此辅助功能设置才能正常工作。

Related MCP server: OpenAI Agents MCP Server

特征

Web 内容提取：自动提取 Web 内容并将其格式化为 Markdown
文章标题提取：提取并显示文章标题
图像处理：可选地对网页中的图像进行优化处理（默认情况下禁用，使用enableFetchImages: true启用）
分页支持：支持文本和图像的分页
JPEG 优化：自动将图像优化为 JPEG 以获得更好的性能
GIF 支持：从动画 GIF 中提取第一帧

对于开发人员

以下部分适用于那些想要开发或修改该工具的人。

先决条件

Node.js 18+
macOS（用于剪贴板操作）
Claude Desktop（从https://claude.ai/desktop安装）
tsx（通过npm install -g tsx ）

安装

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

图像处理规格

处理来自 Web 内容的图像时，将应用以下优化：

图像被转换为 JPEG 格式并进行质量控制
最大宽度默认限制为 1200px
默认最大高度限制为 1600px
色度子采样（4:2:0）可实现更好的压缩
MozJPEG 优化，可实现更小的文件大小

配置

确保 Claude Desktop 已安装并正在运行。
如果还没有安装 tsx，请全局安装：

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

修改位于以下位置的 Claude Desktop 配置： ~/Library/Application Support/Claude/claude_desktop_config.json

您可以通过 Claude Desktop 菜单轻松找到它：

打开 Claude 桌面
在 Mac 菜单栏上单击 Claude
点击“设置”
点击“开发者”

将以下内容添加到您的 MCP 客户端的配置中：

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

可用参数

url （必填）：要获取的 URL
maxLength （默认值：20000）：返回内容的最大长度
startIndex （默认值：0）：内容中的起始位置
imageStartIndex （默认值：0）：图像收集的起始位置
raw （默认值：false）：返回原始内容而不是处理过的 markdown
imageMaxCount （默认值：3）：每个请求处理的最大图像数量
imageMaxHeight （默认值：4000）：合并图像的最大高度
imageMaxWidth （默认值：1000）：合并图像的最大宽度
imageQuality （默认值：80）：JPEG 质量（1-100）
enableFetchImages （默认值：false）：启用图像获取和处理功能。仅限 CLAUDE 用户：您可以启用此功能！CLAUDE 可以获取和处理图像！尽情享受这项功能吧！
ignoreRobotsTxt （默认值：false）：忽略 robots.txt 限制

示例

基本内容获取（无图像）

{
  "url": "https://example.com"
}

启用图片抓取

{
  "url": "https://example.com",
  "enableFetchImages": true,
  "imageMaxCount": 3
}

通过图像分页

{
  "url": "https://example.com",
  "enableFetchImages": true,
  "imageStartIndex": 3,
  "imageMaxCount": 3
}

笔记

由于此工具依赖于 macOS 特定的剪贴板操作，因此仅适用于 macOS。
使用 Sharp 处理图像以获得最佳性能和质量。
当发现多幅图像时，它们会垂直合并，同时考虑尺寸限制。
通过提取动画 GIF 的第一帧来自动处理动画 GIF。

变更日志

v1.1.3

更改了默认行为：默认情况下不获取图像（ enableFetchImages: false ）
删除disableImages ，改为使用enableFetchImages参数

v1.1.0

增加文章标题提取功能
改进了响应格式以包含文章标题
修复了 MCP 响应内容的类型问题

v1.0.0

初始版本
网页内容提取
图像处理与优化
分页支持

Available Tools

1 tool

imageFetchA

画像取得に強いMCPフェッチツール。記事本文をMarkdown化し、ページ内の画像を抽出・最適化して返します。

新APIの既定（imagesを指定した場合）

画像: 取得してBASE64で返却（最大3枚を縦結合した1枚JPEG）
保存: しない（オプトイン）
クロスオリジン: 許可（CDN想定）

パラメータ（新API）

url: 取得先URL（必須）
images: true | { output, layout, maxCount, startIndex, size, originPolicy, saveDir }
- output: "base64" | "file" | "both"（既定: base64）
- layout: "merged" | "individual" | "both"（既定: merged）
- maxCount/startIndex（既定: 3 / 0）
- size: { maxWidth, maxHeight, quality }（既定: 1000/1600/80）
- originPolicy: "cross-origin" | "same-origin"（既定: cross-origin）
text: { maxLength, startIndex, raw }（既定: 20000/0/false）
security: { ignoreRobotsTxt }（既定: false）

旧APIキー（enableFetchImages, returnBase64, saveImages, imageMax*, imageStartIndex 等）は後方互換のため引き続き受け付けます（非推奨）。

Examples（新API） { "url": "https://example.com", "images": true }

{ "url": "https://example.com", "images": { "output": "both", "layout": "both", "maxCount": 4 } }

Examples（旧API互換） { "url": "https://example.com", "enableFetchImages": true, "returnBase64": true, "imageMaxCount": 2 }

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes
`maxLength`	No
`startIndex`	No
`imageStartIndex`	No
`raw`	No
`imageMaxCount`	No
`imageMaxHeight`	No
`imageMaxWidth`	No
`imageQuality`	No
`enableFetchImages`	No
`allowCrossOriginImages`	No
`ignoreRobotsTxt`	No
`saveImages`	No
`returnBase64`	No
`images`	No
`text`	No
`security`	No

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It details behavioral traits: images are fetched, base64 returned (default), max 3 images merged into one JPEG, no save unless opted in, cross-origin allowed, and old API compatibility. Absent are rate limits or auth needs, but core behavior is transparent.

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

Conciseness3/5

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

The description is lengthy (≈250 words) but well-structured with sections for defaults, parameters, and examples. It is front-loaded with purpose but contains redundant details (e.g., repeating default values in both text and examples). Could be more concise.

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

Completeness4/5

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

Given the tool's complexity (17 parameters, nested objects, no output schema), the description provides extensive detail on new API behavior, defaults, and legacy support. Includes examples. Does not explicitly explain return format beyond base64 and Markdown, but contextually sufficient.

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

Parameters4/5

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

Schema coverage is 0%, so description must compensate. It lists parameters for the new API (images object with output, layout, maxCount, etc.) and mentions old keys. It covers defaults and options, though some top-level schema parameters (e.g., maxLength, startIndex) are explained only under the text object, causing slight ambiguity.

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 it is an MCP fetch tool specialized for image acquisition, converting article text to Markdown and extracting/optimizing images. It specifies verb+resource (fetch and process web pages with images) and no sibling tools exist, so no differentiation needed.

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

Usage Guidelines4/5

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

The description explains when to use (for fetching pages with images) and provides detailed parameter behavior for both new and legacy APIs. It does not explicitly exclude scenarios but offers enough context for appropriate use.

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 tool updatev1.6.2May 3, 2026

ChangedimageFetch4 fields changed

addedInput schema / properties / allowCrossOriginImages

Added value: +{
+  "default": true,
+  "type": [
+    "boolean",
+    "string"
+  ]
+}

addedInput schema / properties / images

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "layout": {
+          "enum": [
+            "merged",
+            "individual",
+            "both"
+          ],
+          "type": "string"
+        },
+        "maxCount": {
+          "maximum": 10,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "originPolicy": {
+          "enum": [
+            "cross-origin",
+            "same-origin"
+          ],
+          "type": "string"
+        },
+        "output": {
+          "enum": [
+            "base64",
+            "file",
+            "both"
+          ],
+          "type": "string"
+        },
+        "saveDir": {
+          "type": "string"
+        },
+        "size": {
+          "additionalProperties": false,
+          "properties": {
+            "maxHeight": {
+              "maximum": 10000,
+              "minimum": 100,
+              "type": "integer"
+            },
+            "maxWidth": {
+              "maximum": 10000,
+              "minimum": 100,
+              "type": "integer"
+            },
+            "quality": {
+              "maximum": 100,
+              "minimum": 1,
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "startIndex": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  ]
+}

addedInput schema / properties / security

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "ignoreRobotsTxt": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / text

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "maxLength": {
+      "exclusiveMinimum": 0,
+      "maximum": 1000000,
+      "type": "integer"
+    },
+    "raw": {
+      "type": "boolean"
+    },
+    "startIndex": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

1 tool updatev1.0.0Aug 18, 2025
- First observedimageFetch

Deploy Server

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

TDQS

A4.4/5.0

Scored 2026-05-03 15:00 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.

Naming Consistency5/5

The single tool name 'imageFetch' is descriptive and follows a verb_noun pattern. There is no inconsistency since only one tool exists.

Tool Count4/5

While the server has only one tool, it is a complex and well-documented tool that handles a wide range of functionality appropriate for its fetch-image purpose. The count is slightly below the typical range but not insufficient.

Completeness5/5

The tool comprehensively covers fetching web pages, extracting images, and outputting them in various formats (base64, file, merged, individual). It includes parameters for text extraction and security, leaving no apparent gaps for its stated purpose.

Maintenance

ActivityInactive

ResponsivenessSlow

Resources

Need Help?

Related Servers

Related MCP Connectors

Firecrawl MCP Server A
io.github.firecrawl
MCP server for Firecrawl — web search, scraping, and biomedical/arXiv paper search.
Browser Automation Web Scraping Search
317,586
Sentry AOAuth
dev.sentry.mcp
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Monitoring Developer Tools Observability
3
Apideck MCP A
dev.apideck.mcp
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Developer Tools
42
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238

Related MCP Servers

MCP Server Example
Developer Tools Code Execution Autonomous Agents
alejandro-ao
A
license
B
quality
D
maintenance
An educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.
Updated a year ago (2025-04-29 10:58 UTC)
1
162
MIT
OpenAI Agents MCP Server
Agent Orchestration Search RAG Systems
lroolle
F
license
B
quality
D
maintenance
A Model Context Protocol server that enables Claude users to access specialized OpenAI agents (web search, file search, computer actions) and a multi-agent orchestrator through the MCP protocol.
Updated 2 years ago (2025-03-14 16:23 UTC)
4
10
-
MCP Fetch
Browser Automation Image & Video Processing Web Scraping
JeremyNixon
A
license
A
quality
D
maintenance
Model Context Protocol server that enables Claude Desktop (or any MCP client) to fetch web content and process images appropriately.
Updated 2 years ago (2025-01-12 09:51 UTC)
1
141 npm
MIT
URL Fetch MCP
Browser Automation Web Scraping
aelaguiz
A
license
A
quality
D
maintenance
A Model Context Protocol (MCP) server that enables Claude or other LLMs to fetch content from URLs, supporting HTML, JSON, text, and images with configurable request parameters.
Updated 2 years ago (2025-03-19 04:18 UTC)
3
3
MIT

MCP 获取

快速入门（针对用户）

所需设置

特征

对于开发人员

先决条件

安装

图像处理规格

配置

可用参数

示例

基本内容获取（无图像）

启用图片抓取

通过图像分页

笔记

变更日志

v1.1.3

v1.1.0

v1.0.0

Available Tools

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

MCP Server Example

OpenAI Agents MCP Server

MCP Fetch

URL Fetch MCP

Appeared in Searches