ZapFetch MCP Server

MCP开发工具

提供方 zapfetch

开发工具 未标注 API Key 社区 / 第三方

An APAC-native web scraping API for AI agents that provides tools for scraping, crawling, searching, and extracting structured data from websites, directly usable from MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.

一句话选型结论

按资料字段整理

ZapFetch MCP Server 属于开发工具类 MCP 服务器,传输方式未标注,API Key,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权API Key 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
ZapFetch MCP Server当前 未标注 未标注 支持远程部署 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方zapfetch上游标注的维护方 zapfetch
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

8.2 KB
来自项目仓库与上游目录的原文,未做删改

@zapfetchdev/mcp-server

MCP (Model Context Protocol) server for ZapFetch — APAC-native web scraping API for AI agents.

Use ZapFetch directly from Claude Desktop, Cursor, Windsurf, and any other MCP-compatible client.

Tools

  • zapfetch_scrape — scrape a single URL
  • zapfetch_search — web search with optional content extraction
  • zapfetch_crawl — crawl a website (async, returns job_id)
  • zapfetch_crawl_status — poll crawl job progress
  • zapfetch_map — discover URLs on a site (fast, no content)
  • zapfetch_extract — extract structured data with a prompt + schema
  • zapfetch_extract_status — poll extract job progress

Docs: https://docs.zapfetch.com

For docs lookups, Claude/Cursor/Windsurf can also use the auto-generated Mintlify MCP at https://docs.zapfetch.com/mcp.

Prerequisites

  • Node.js 20+
  • A ZapFetch API key (get one here)

Install```bash

npm install -g @zapfetchdev/mcp-server


## Configure

### Claude Desktop

Edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):```json
{
  "mcpServers": {
    "zapfetch": {
      "command": "npx",
      "args": ["-y", "@zapfetchdev/mcp-server"],
      "env": {
        "ZAPFETCH_API_KEY": "zf-your-api-key"
      }
    }
  }
}

Cursor

Edit ~/.cursor/mcp.json:```json
{
"mcpServers": {
"zapfetch": {
"command": "npx",
"args": ["-y", "@zapfetchdev/mcp-server"],
"env": { "ZAPFETCH_API_KEY": "zf-your-api-key" }
}
}
}


### Windsurf

Edit `~/.codeium/windsurf/mcp_config.json`:```json
{
  "mcpServers": {
    "zapfetch": {
      "command": "npx",
      "args": ["-y", "@zapfetchdev/mcp-server"],
      "env": { "ZAPFETCH_API_KEY": "zf-your-api-key" }
    }
  }
}

Install via Smithery

For a one-command install that auto-writes the config for your MCP client:```bash
npx -y @smithery/cli install @zapfetchdev/mcp-server --client claude

or --client cursor, --client windsurf


Smithery will prompt for your ZapFetch API key once, then register the server in the right config file for you. This invokes the package's STDIO entry (`bin.zapfetch-mcp` → `dist/index.js`) — identical to the manual configs above.

## Environment Variables

| Variable            | Required | Default                   | Description                  |
|---------------------|----------|---------------------------|------------------------------|
| `ZAPFETCH_API_KEY`  | STDIO    | —                         | Your ZapFetch API key (STDIO mode only — HTTP mode takes the key per-request via `Authorization: Bearer`) |
| `ZAPFETCH_API_URL`  | no       | `https://api.zapfetch.com`| Override for self-host / dev |
| `PORT`              | HTTP     | `3000`                    | HTTP server port (HTTP mode only) |
| `ZAPFETCH_TRANSPORT`| Docker   | `stdio`                   | Inside the Docker image only, switches between `stdio` / `http` via `entry.sh`. Ignored by the `zapfetch-mcp` / `zapfetch-mcp-http` npm binaries. |

## Usage Examples

After configuration, ask your AI assistant naturally — it will pick the right tool automatically.

### Scrape a single page

> "Scrape https://rakuten.co.jp and give me the main content as markdown."

Uses `zapfetch_scrape`. Best for a known URL where you want raw page content quickly. If the page is geo-blocked or returns sparse content, follow up with a search instead.

### Search the web

> "Find the top 5 recent blog posts about TypeScript 5.7 and summarize each one."

Uses `zapfetch_search`. Returns ranked results with optional content extraction. Useful when you don't have a specific URL yet, or as a fallback when a direct scrape comes up empty.

### Crawl a site (multi-page)

> "Crawl https://docs.example.com starting from the root, up to 50 pages, and summarize the authentication section."

Uses `zapfetch_crawl` to kick off an async job (returns a `job_id`), then `zapfetch_crawl_status` to poll until complete. The assistant handles the polling loop — you just wait for the result.

**Tip:** For large sites, map first (see below) to identify which URLs are worth crawling before committing.

### Map a site (URL discovery)

> "List all URLs under https://docs.example.com/api so I can decide which pages to scrape."

Uses `zapfetch_map`. Returns URLs only — no content fetched — so it's fast even on large sites. Pair with `zapfetch_scrape` to cherry-pick the pages you actually need:

> "Map https://stripe.com/docs, then scrape the 3 pages most relevant to webhook setup."

### Extract structured data

> "Extract product name, price, currency, and stock status from these 5 rakuten.co.jp product URLs. Return as a JSON array."

Uses `zapfetch_extract` with a prompt and optional JSON schema. The job is async — `zapfetch_extract_status` polls it to completion. Good for turning arbitrary product pages, job listings, or articles into structured records at scale.

### Poll extract job status

> "Check whether the extract job job_abc123 is done."

Uses `zapfetch_extract_status` directly. You rarely need to ask for this by name — the assistant calls it automatically after `zapfetch_extract` — but it's useful if you started a job in a previous session and want to retrieve results later.

### Combining tools

Tools compose naturally. A few common patterns:

- **Survey then scrape:** map a large site to get all URLs, filter to the relevant ones, scrape each.
- **Search then scrape:** search to find the canonical source for a topic, then scrape that page for full content.
- **Scrape with fallback:** if `zapfetch_scrape` returns thin content (e.g. JS-heavy page), the assistant can fall back to `zapfetch_search` to find a cached or mirror version.

## Migrating from Firecrawl MCP

ZapFetch is Firecrawl-compatible at the API level, but this MCP uses `zapfetch_*` tool names (not `firecrawl_*`) to avoid conflicts if you run both. Capabilities are 1:1 — just update prompts referring to tool names.

## HTTP transport (self-hosted)

For hosted / multi-tenant deployments, run the HTTP server instead of STDIO. Each request carries its own API key via `Authorization: Bearer`, so a single deployment can serve many users without sharing credentials.

### Docker```bash
docker run -d \
  -p 3000:3000 \
  -e ZAPFETCH_TRANSPORT=http \
  docker.io/zapfetchdev/mcp:latest

From npm```bash

npm install -g @zapfetchdev/mcp-server

then run the HTTP entry (never the STDIO one in this mode)

zapfetch-mcp-http


### Endpoints

| Path | Auth | Behavior |
|------|------|----------|
| `GET /health` | none | Returns `{ok:true, version, transport:"http"}`. Use for container health checks. |
| `POST /mcp`   | `Authorization: Bearer ` required | MCP JSON-RPC endpoint. Requests MUST include `Accept: application/json, text/event-stream` per MCP spec. |

### Example call```bash
curl -X POST http://localhost:3000/mcp \
  -H "Authorization: Bearer fc-YOUR-KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Security notes

  • Do not set ZAPFETCH_API_KEY in HTTP mode. The server refuses to start (exit code 2) if the env var is present — this prevents a misconfigured container from silently serving every request from the operator's key.
  • The HTTP server is stateless: each request builds its own transport + client, with the Bearer token flowing to the MCP tool handler via the SDK's native extra.authInfo.token channel. No cross-request state, no session leaks.
  • Upstream ZapFetch API error strings are sanitized before transiting to HTTP clients — only a small allowlist of error codes (rate_limit, invalid_key, quota_exceeded, upstream_unavailable) passes through.
  • The stderr access log is strict-allowlist: only ts / method / path / status / ms / origin_ip. Bearer tokens, bodies, and headers are never logged.

Development```bash

pnpm install # or npm install
npm run typecheck
npm run build # -> dist/


Local test with Claude Desktop pointed at your build:```json
{
  "mcpServers": {
    "zapfetch-dev": {
      "command": "node",
      "args": ["/absolute/path/to/zapfetch-mcp/dist/index.js"],
      "env": { "ZAPFETCH_API_KEY": "zf-..." }
    }
  }
}

License

MIT

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
ZapFetch MCP Server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

ZapFetch MCP Server 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

ZapFetch MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

ZapFetch MCP Server 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

ZapFetch MCP Server 能提供哪些能力?

资料显示能力标签包括 API密钥、开发工具、命令行工具。具体工具清单以官方文档为准。

ZapFetch MCP Server 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

ZapFetch MCP Server 是本地还是远程?

它是远程端点,连服务地址即可。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。