Agentfetch MCP Server

Token-budgeted web fetch for AI agents — auto-routes Jina, FireCrawl, Trafilatura, PDF.

Remote serverstreamable-httpPython

What is the Agentfetch MCP server?

Token-budgeted web fetch for AI agents — auto-routes Jina, FireCrawl, Trafilatura, PDF. The agentfetch mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.

What it actually does

AgentFetch sits between your agent and the open web. Instead of integrating Jina, FireCrawl, pypdf, and your own caching layer separately, agents call one MCP tool and AgentFetch handles routing, caching, token budgeting, and clean Markdown extraction automatically.

  • Trafilatura — (free, local) for ~70% of standard web pages
  • Jina Reader — for the rest of HTML
  • FireCrawl — for JS-heavy pages (Twitter/X, LinkedIn, Notion, etc.)
  • pypdf — for PDFs (zero external cost)

Its toolset

Everything the assistant can do here goes through one of these:

  • Pay-per — call pricing from $0.001/fetch
  • fetch_url — Fetch a URL → clean Markdown + metadata + token count + cache info
  • estimate_tokens — Get a token count before fetching, so agents don't blow context windows on huge pages
  • fetch_multiple — Fetch up to 20 URLs concurrently
  • search_and_fetch — Web search + fetch top N results in one round-trip
  • Feature — AgentFetch
  • JINA_API_KEY — Recommended
  • FIRECRAWL_API_KEY — Optional
  • REDIS_URL — Optional
  • CACHE_TTL_SECONDS — Optional

Configuration

You will need 3 environment variables: JINA_API_KEY, FIRECRAWL_API_KEY, REDIS_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of search and retrieval servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agentfetch's toolset — Pay-per, fetch_url, estimate_tokens and 7 more — is a fair guide to whether it matches your workflow. It is maintained by bch1212; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Agentfetch.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the agentfetch mcp server does with a few real requests.

Available tools

ToolWhat it does
Pay-percall pricing from $0.001/fetch
fetch_urlFetch a URL → clean Markdown + metadata + token count + cache info
estimate_tokensGet a token count *before* fetching, so agents don't blow context windows on huge pages
fetch_multipleFetch up to 20 URLs concurrently
search_and_fetchWeb search + fetch top N results in one round-trip
FeatureAgentFetch
JINA_API_KEYRecommended
FIRECRAWL_API_KEYOptional
REDIS_URLOptional
CACHE_TTL_SECONDSOptional

How to install the Agentfetch MCP server

{
  "mcpServers": {
    "agentfetch": {
      "command": "uvx",
      "args": ["agentfetch-mcp"],
      "env": {
        "JINA_API_KEY": "your-value",
        "FIRECRAWL_API_KEY": "your-value",
        "REDIS_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
JINA_API_KEYCredential the server authenticates with.Yes
FIRECRAWL_API_KEYCredential the server authenticates with.Yes
REDIS_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Agentfetch to Pay-per.
  • Use Agentfetch to fetch url.
  • Use Agentfetch to estimate tokens.

Frequently asked questions

It connects Agentfetch to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (Pay-per, fetch_url, estimate_tokens, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agentfetch directly.