Skip to main content
Glama
enesjakozh
JeremyNixon

MCP Fetch

by JeremyNixon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

MCP 페치

대장간 배지

웹 콘텐츠를 가져오고 이미지를 처리하는 모델 컨텍스트 프로토콜 서버입니다. 이를 통해 Claude Desktop(또는 모든 MCP 클라이언트)이 웹 콘텐츠를 가져오고 이미지를 적절하게 처리할 수 있습니다.

빠른 시작(사용자용)

Claude Desktop과 함께 이 도구를 사용하려면 Claude Desktop 구성에 다음을 추가하기만 하면 됩니다( ~/Library/Application Support/Claude/claude_desktop_config.json ):

지엑스피1

필요할 때 도구의 최신 버전이 자동으로 다운로드되어 실행됩니다.

필수 설정

  1. Claude의 접근성 활성화:

    • 시스템 설정 열기

    • 개인정보 보호 및 보안 > 접근성으로 이동하세요

    • "+" 버튼을 클릭하세요

    • 응용 프로그램 폴더에서 Claude를 추가하세요

    • Claude의 토글을 켜세요

이 접근성 설정은 자동 클립보드 작업(Cmd+V)이 제대로 작동하는 데 필요합니다.

Related MCP server: @kazuph/mcp-fetch

개발자를 위한

다음 섹션은 도구를 개발하거나 수정하려는 사람들을 위한 것입니다.

필수 조건

  • 노드.js 18+

  • macOS(클립보드 작업용)

  • Claude Desktop( https://claude.ai/desktop 에서 설치)

  • tsx ( npm install -g tsx 를 통해 설치)

설치

Smithery를 통해 설치

Smithery 를 통해 Claude Desktop용 MCP Fetch를 자동으로 설치하려면:

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

수동 설치

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

이미지 처리 사양

웹 콘텐츠의 이미지를 처리할 때 다음과 같은 제한이 적용됩니다.

  • 그룹당 최대 6개의 이미지

  • 그룹당 최대 높이 8000픽셀

  • 그룹당 최대 크기 30MB

콘텐츠가 이러한 제한을 초과하면 이미지는 자동으로 여러 그룹으로 분할되며, 여러 번 붙여넣기(Cmd+V)를 해야 합니다.

구성

  1. Claude Desktop이 설치되어 실행 중인지 확인하세요.

  2. 아직 설치하지 않았다면 tsx를 전역적으로 설치하세요.

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

  1. ~/Library/Application Support/Claude/claude_desktop_config.json 에 있는 Claude Desktop 구성을 수정하세요.

Claude Desktop 메뉴를 통해 쉽게 찾을 수 있습니다.

  1. 클로드 데스크톱 열기

  2. Mac 메뉴 막대에서 Claude를 클릭하세요

  3. "설정"을 클릭하세요

  4. "개발자"를 클릭하세요

MCP 클라이언트 구성에 다음을 추가하세요.

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

사용 가능한 도구

  • fetch : 인터넷에서 URL을 가져와 마크다운 형식으로 추출합니다. 이미지는 자동으로 처리되어 클립보드 작업에 사용할 수 있도록 준비됩니다.

노트

  • 이 도구는 macOS 특정 클립보드 작업에 종속되기 때문에 macOS용으로만 설계되었습니다.

  • 최적의 성능과 품질을 위해 Sharp를 사용하여 이미지를 처리합니다.

  • 여러 개의 이미지가 발견되면 크기 제한을 고려하여 수직으로 병합됩니다.

  • 애니메이션 GIF는 첫 번째 프레임을 추출하여 자동으로 처리됩니다.

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