Skip to main content
Glama
deenesjakoruzh
gregberns

Fetch-Save MCP Server

by gregberns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

获取-保存 MCP 服务器

提供 Web 内容获取和本地文件保存功能的模型上下文协议 (MLM) 服务器。该服务器使 LLM 能够从网页检索内容，将 HTML 转换为 Markdown 以便于使用，并将检索到的内容保存到本地文件。

与标准获取 MCP 服务器的主要区别在于，该服务器提供了一个获取-保存工具，既可以检索内容，又可以在本地将其存储在永久文件中，以便以后访问或处理数据。

此服务器可访问本地/内部 IP 地址，可能存在安全风险。使用此 MCP 服务器时请务必小心，确保不会泄露任何敏感数据。

补充说明：本 Readme 文件和部分代码使用 Claude Code 编写/编辑，因此部分内容可能存在错误。如需修改，请提交 PR。

可用工具

  • fetch-save - 从互联网获取 URL，将其内容提取为 markdown，然后将其保存到本地文件。

    • url （字符串，必需）：获取并下载的 URL

    • filepath （字符串，必需）：下载内容将保存的本地文件路径

Related MCP server: MCP URL Fetcher

提示

  • 获取-保存

    • 获取 URL 并将其内容保存到本地文件

    • 参数：

      • url （字符串，必需）：获取并下载的 URL

      • filepath （字符串，必需）：将保存内容的本地文件路径

安装

可选：安装 node.js，这将导致 fetch 服务器使用更强大的不同 HTML 简化器。

使用 uv（推荐）

使用uv时无需特殊安装。我们将使用uvx直接运行mcp-server-fetch-save 。

使用 PIP

或者，您可以通过 pip 安装mcp-server-fetch-save ：

pip install mcp-server-fetch-save

安装后，您可以使用以下命令将其作为脚本运行：

python -m mcp_server_fetch_save

配置

为 Claude.app 配置

添加到您的 Claude 设置：

"mcpServers": {
  "fetch-save": {
    "command": "uvx",
    "args": ["mcp-server-fetch-save"]
  }
}
"mcpServers": {
  "fetch-save": {
    "command": "python",
    "args": ["-m", "mcp_server_fetch_save"]
  }
}

配置 VS Code

如需手动安装，请将以下 JSON 块添加到 VS Code 中的“用户设置 (JSON)”文件中。您可以按下Ctrl + Shift + P并输入Preferences: Open User Settings (JSON)来执行此操作。

或者，您可以将其添加到工作区中名为.vscode/mcp.json的文件中。这样您就可以与其他人共享该配置。

请注意，使用mcp.json文件时需要mcp密钥。

{
  "mcp": {
    "servers": {
      "fetch-save": {
        "command": "uvx",
        "args": ["mcp-server-fetch-save"]
      }
    }
  }
}

自定义 - robots.txt

默认情况下，如果请求来自模型（通过工具），服务器将遵循网站 robots.txt 文件的规则；但如果请求是由用户发起的（通过提示）。可以通过在配置文件的args列表中添加参数--ignore-robots-txt来禁用此功能。

定制 - 用户代理

默认情况下，根据请求是来自模型（通过工具）还是用户发起（通过提示），服务器将使用用户代理

ModelContextProtocol/1.0 (Autonomous; +https://github.com/modelcontextprotocol/servers)

或者

ModelContextProtocol/1.0 (User-Specified; +https://github.com/modelcontextprotocol/servers)

可以通过将参数--user-agent=YourUserAgent添加到配置中的args列表来进行定制。

定制 - 代理

可以使用--proxy-url参数将服务器配置为使用代理。

调试

您可以下载此 repo，并将其添加到您的.mcp.json文件以在本地运行/测试。

{
  "mcpServers": {
    "fetch_save": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/clone/of/project/mcp-server-fetch-save/src/mcp_server_fetch_save",
        "run",
        "__main__.py"
      ]
    }
  }
}

您可以使用 MCP 检查器来调试服务器。对于 uvx 安装：

npx @modelcontextprotocol/inspector uvx mcp-server-fetch-save

或者，如果您已将软件包安装在特定目录中或正在其上进行开发：

cd path/to/mcp-server-fetch-save
npx @modelcontextprotocol/inspector uv run mcp-server-fetch-save

贡献

我们鼓励您为扩展和改进 mcp-server-fetch-save 做出贡献。无论您是想添加新工具、增强现有功能还是改进文档，您的贡献都弥足珍贵。

有关其他 MCP 服务器和实现模式的示例，请参阅： https://github.com/modelcontextprotocol/servers

欢迎提交 Pull 请求！欢迎贡献新想法、错误修复或改进，让 mcp-server-fetch-save 更加强大实用。

执照

mcp-server-fetch-save 采用 MIT 许可证。这意味着您可以自由使用、修改和分发该软件，但须遵守 MIT 许可证的条款和条件。更多详情，请参阅项目仓库中的 LICENSE 文件。

谢谢

该服务器是基于原始modelcontextprotocol/servers获取服务器开发的，并增加了将内容保存到本地文件的功能。

Available Tools

1 tool
fetch-saveA

Fetches a URL from the internet and SAVES the contents to a LOCAL FILE. This tool is specifically designed for DOWNLOADING and STORING web content to your filesystem.

When you need to both access online content AND save it locally for later use or processing, THIS is the appropriate tool to use. Unlike the regular fetch tool which only displays content, this tool permanently stores the fetched data in a file.

Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that.

ParametersJSON Schema
NameRequiredDescriptionDefault
filepathYesLocal filepath where the downloaded content will be saved
urlYesURL to fetch and download for local storage

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: that the tool performs a download operation, permanently stores data to the filesystem, grants internet access capability, and fetches up-to-date information. However, it doesn't mention potential limitations like file size constraints, network timeouts, or error handling scenarios.

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 appropriately front-loaded with the core functionality, but contains some redundant phrasing and historical context about internet access that could be more concise. The third paragraph about previously lacking internet access adds context but could be integrated more efficiently into the usage guidelines.

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?

For a tool with 2 parameters, 100% schema coverage, and no annotations or output schema, the description provides good contextual completeness. It explains the tool's purpose, usage context, behavioral characteristics, and internet access capability. The main gap is the lack of information about return values or error conditions, which would be helpful given there's no output schema.

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

Parameters3/5

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

The input schema has 100% description coverage, providing clear documentation for both parameters. The description adds some context by mentioning 'downloading and storing web content' and 'local file for storage and future use,' but doesn't provide additional semantic details beyond what's already in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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 ('fetches', 'saves', 'downloading', 'storing') and resources ('URL', 'web content', 'local file', 'filesystem'). It explicitly distinguishes this from a hypothetical 'regular fetch tool' that only displays content, establishing clear differentiation even without actual sibling tools.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'When you need to both access online content AND save it locally for later use or processing, THIS is the appropriate tool to use.' It also clearly contrasts with an alternative ('regular fetch tool which only displays content') and specifies the tool's internet access capability that overrides previous limitations.

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 updatev1.0.0
    • First observedfetch-save
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

A4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined as fetching and saving web content, making it distinct by default.

Naming Consistency5/5

The single tool name 'fetch-save' follows a consistent verb-verb pattern that clearly describes its dual functionality. There are no other tools to compare against, so consistency is inherently perfect.

Tool Count2/5

A single tool is too few for a server named 'Fetch-Save MCP Server', which implies a broader scope of operations. While the tool itself is useful, the server lacks complementary tools like list, delete, or manage saved files, making it feel incomplete and thin for its apparent purpose.

Completeness2/5

The server is severely incomplete for a fetch-and-save domain. It only provides a download-and-store operation, with no tools for managing saved files (e.g., list, read, delete, update) or handling errors, which will limit agent workflows and cause dead ends in tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches