Fetch vs Scrapi

A side-by-side look at the Fetch and Scrapi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Fetch logoFetchSearch & Data Extraction · Local subprocess (stdio)Web content fetching and conversion for efficient LLM usage.90ExcellentAuth: no auth requiredScrapi logoScrapiSearch & Data Extraction · Local subprocess (stdio)Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.59GoodAuth: not declared

Verdict: choose Fetch for search & data extraction work as a local process; choose Scrapi 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?

Fetch logoChoose 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 create_entities, create_relations, add_observations.
Explore Fetch

Scrapi logoChoose Scrapi when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SCRAPI_API_KEY.
  • You want tools like scrape_url, scrape_urls, get_usage.
Explore Scrapi

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFetch logoFetchScrapi logoScrapi
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal90/100 · Excellent59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedSCRAPI_API_KEY
Verified owner VerifiedCommunity listing
GitHub stars91,4055
Directory activity 5 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools95

Tools & capabilities

Fetch tools 9

  • create_entitiesCreate multiple new entities in the knowledge graph
  • create_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voice
  • add_observationsAdd new observations to existing entities in the knowledge graph
  • delete_entitiesDelete multiple entities and their associated relations from the knowledge graph
  • delete_observationsDelete specific observations from entities in the knowledge graph
  • delete_relationsDelete multiple relations from the knowledge graph
  • read_graphRead the entire knowledge graph
  • search_nodesSearch for nodes in the knowledge graph based on a query
  • open_nodesOpen specific nodes in the knowledge graph by their names

Scrapi tools 5

  • scrape_urlScrapes a webpage and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.
  • scrape_urlsScrapes multiple webpages in parallel and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.
  • get_usageCheck API usage and remaining credits. Returns current plan, subscription credits, purchased credits, and total remaining credits.
  • scraper_server_statusCheck the status of all ScraperServer instances. Shows server health, circuit breaker state, failure counts, and last success/failure times.
  • get_billingRetrieve MCP billing information: subscription details, available plans, daily usage history, or spending limits.

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.

Fetch

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

Scrapi

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "scrapi": {
      "command": "npx",
      "args": [
        "-y",
        "@scrapi.ai/mcp-server"
      ],
      "env": {
        "SCRAPI_API_KEY": "YOUR_SCRAPI_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Fetch is categorized under Search & Data Extraction and uses a local stdio subprocess. Scrapi belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Fetch for search & data extraction work and Scrapi 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.

Fetch is listed as free. Auth: no auth required. Scrapi has no declared pricing — check the project's own site. 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 fetch and scrapi as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Fetch has a quality signal of 90/100 (Excellent) with 5 views, 0 installs and 91,405 GitHub stars. Scrapi has 59/100 (Good) with 1 views, 0 installs and 5 GitHub stars.