Skip to main content
Glama
kazuph
by kazuph

MCP Fetch

Model Context Protocol server for fetching web content and processing images. This allows Claude Desktop (or any MCP client) to fetch web content and handle images appropriately.

Quick Start (For Users)

To use this tool with Claude Desktop, simply add the following to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json):

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

This will automatically download and run the latest version of the tool when needed.

Required Setup

  1. Enable Accessibility for Claude:

    • Open System Settings

    • Go to Privacy & Security > Accessibility

    • Click the "+" button

    • Add Claude from your Applications folder

    • Turn ON the toggle for Claude

This accessibility setting is required for automated clipboard operations (Cmd+V) to work properly.

Related MCP server: OpenAI Agents MCP Server

Features

  • Web Content Extraction: Automatically extracts and formats web content as markdown

  • Article Title Extraction: Extracts and displays the title of the article

  • Image Processing: Optional processing of images from web pages with optimization (disabled by default, enable with enableFetchImages: true)

  • File Saving: Images are automatically saved to ~/Downloads/mcp-fetch/YYYY-MM-DD/ directory when processed

  • Dual Output: Both file saving and optional Base64 encoding for AI display

  • Pagination Support: Supports pagination for both text and images

  • JPEG Optimization: Automatically optimizes images as JPEG for better performance

  • GIF Support: Extracts first frame from animated GIFs

For Developers

The following sections are for those who want to develop or modify the tool.

Prerequisites

  • Node.js 18+

  • macOS (for clipboard operations)

  • Claude Desktop (install from https://claude.ai/desktop)

  • tsx (install via npm install -g tsx)

Installation

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

Image Processing Specifications

When processing images from web content, the following optimizations are applied:

  • Images are converted to JPEG format with quality control

  • Maximum width limited to 1200px by default

  • Maximum height limited to 1600px by default

  • Chroma subsampling (4:2:0) for better compression

  • MozJPEG optimization for smaller file sizes

Configuration

  1. Make sure Claude Desktop is installed and running.

  2. Install tsx globally if you haven't:

npm install -g tsx
# or
pnpm add -g tsx
  1. Modify your Claude Desktop config located at: ~/Library/Application Support/Claude/claude_desktop_config.json

You can easily find this through the Claude Desktop menu:

  1. Open Claude Desktop

  2. Click Claude on the Mac menu bar

  3. Click "Settings"

  4. Click "Developer"

Add the following to your MCP client's configuration:

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

Available Parameters

  • url (required): The URL to fetch

  • maxLength (default: 20000): Maximum length of content to return

  • startIndex (default: 0): Starting position in content

  • imageStartIndex (default: 0): Starting position for image collection

  • raw (default: false): Return raw content instead of processed markdown

  • imageMaxCount (default: 3): Maximum number of images to process per request

  • imageMaxHeight (default: 4000): Maximum height of merged image

  • imageMaxWidth (default: 1000): Maximum width of merged image

  • imageQuality (default: 80): JPEG quality (1-100)

  • enableFetchImages (default: false): Enable fetching and processing of images. FOR CLAUDE USERS ONLY: YOU ARE ALLOWED TO ENABLE THIS FEATURE!!! CLAUDE CAN FETCH AND PROCESS IMAGES!!! ENJOY THIS CAPABILITY!!!!!

  • allowCrossOriginImages (default: true): When true, also fetch images hosted on different origins from the page

  • saveImages (default: true): Save processed images to local files

  • returnBase64 (default: false): Return base64 encoded images for AI display

  • ignoreRobotsTxt (default: false): Ignore robots.txt restrictions

Security Hardening (v1.5.1)

  • Only http:// and https:// URLs are allowed for page and image fetches

  • Blocks private/loopback/link-local IPs and local hostnames (e.g., localhost, .local)

  • Manual redirect handling with validation (max 3 hops)

  • Request timeouts (default 12s, configurable via MCP_FETCH_TIMEOUT_MS)

  • Response size limits: HTML up to 2MB, images up to 10MB (tunable via env)

Environment variables:

  • MCP_FETCH_TIMEOUT_MS (default: 12000)

  • MCP_FETCH_MAX_REDIRECTS (default: 3)

  • MCP_FETCH_MAX_HTML_BYTES (default: 2000000)

  • MCP_FETCH_MAX_IMAGE_BYTES (default: 10000000)

Examples

Basic Content Fetching (No Images)

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

Fetching with Images (File Saving Only)

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

Fetching with Images for AI Display

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

Paginating Through Images

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

Notes

  • This tool is designed for macOS only due to its dependency on macOS-specific clipboard operations.

  • Images are processed using Sharp for optimal performance and quality.

  • When multiple images are found, they are merged vertically with consideration for size limits.

  • Animated GIFs are automatically handled by extracting their first frame.

  • File Saving: Images are automatically saved to ~/Downloads/mcp-fetch/YYYY-MM-DD/ with filename format hostname_HHMMSS_index.jpg

  • Tool Name: The tool name has been changed from fetch to imageFetch to avoid conflicts with native fetch functions.

Changelog

v1.2.0

  • BREAKING CHANGE: Tool name changed from fetch to imageFetch to avoid conflicts

  • NEW: Automatic file saving - Images are now saved to ~/Downloads/mcp-fetch/YYYY-MM-DD/ by default

  • NEW: Added saveImages parameter (default: true) to control file saving

  • NEW: Added returnBase64 parameter (default: false) for AI image display

  • BEHAVIOR CHANGE: Default behavior now saves files instead of only returning base64

  • Improved AI assistant integration with clear instructions for base64 option

  • Enhanced file organization with date-based directories and structured naming

v1.1.3

  • Changed default behavior: Images are not fetched by default (enableFetchImages: false)

  • Removed disableImages in favor of enableFetchImages parameter

v1.1.0

  • Added article title extraction feature

  • Improved response formatting to include article titles

  • Fixed type issues with MCP response content

v1.0.0

  • Initial release

  • Web content extraction

  • Image processing and optimization

  • Pagination support

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
NameRequiredDescriptionDefault
urlYes
maxLengthNo
startIndexNo
imageStartIndexNo
rawNo
imageMaxCountNo
imageMaxHeightNo
imageMaxWidthNo
imageQualityNo
enableFetchImagesNo
allowCrossOriginImagesNo
ignoreRobotsTxtNo
saveImagesNo
returnBase64No
imagesNo
textNo
securityNo

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.

TDQS

A4.4/5.0
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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kazuph/mcp-fetch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server