ClawPage vs Fetch
A side-by-side look at the ClawPage and Fetch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ClawPage for search & data extraction work as a local process; choose Fetch for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ClawPage when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MCP_PORT. - You want tools like
register, extract_url, account_info.
Choose Fetch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
fetch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 48/100 · Fair | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | MCP_PORT | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,549 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | 1 |
| Full listing | View ClawPage | View Fetch |
Tools & capabilities
ClawPage tools 5
registerCreate account, get API key (cpk_ prefix) with 10 free extractions/dayextract_urlExtract any URL into structured JSON (text, tables, prices, contacts, hours, ratings)account_infoCheck remaining free extractions and USDC balanceadd_walletAssociate wallet address for prepaid USDC depositsdepositCredit balance from on-chain USDC transfer
Fetch tools 1
fetchFetches a URL from the internet and extracts its contents as markdown.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ClawPage
{
"mcpServers": {
"clawpage": {
"command": "npx",
"args": [
"-y",
"clawpage-mcp"
],
"env": {
"MCP_PORT": "YOUR_MCP_PORT_HERE"
}
}
}
}
Fetch
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": [
"mcp-server-fetch"
]
}
}
}
Frequently asked questions
ClawPage is categorized under Search & Data Extraction and uses a local stdio subprocess. Fetch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick ClawPage for search & data extraction work and Fetch for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
ClawPage has no declared pricing — check the project's own site. Fetch is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add clawpage and fetch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ClawPage has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Fetch has 80/100 (Excellent) with 5 views, 0 installs and 91,549 GitHub stars.