Superfetch MCP Server

Superfetch MCP server exists for a simple reason — assistants are far more useful when they can act on Superfetch directly instead of describing what you should do. Intelligent web content fetcher MCP server that converts HTML to clean, AI-readable JSONL format.

What you get

An MCP server that fetches web pages and converts them to clean, readable Markdown.

This server takes a URL, fetches the page, and strips away everything you don't need — navigation, sidebars, banners, scripts — leaving just the main content as Markdown. It's perfect for feeding into LLMs, giving them the distilled essence of a page without the noise. It also recognizes GitHub, GitLab, Bitbucket, and Gist URLs and rewrites them to fetch the raw content directly.

• HTML to Markdown — — Turns any public web page into clean, readable Markdown with metadata like title, url, contentSize, and truncated
• Smart URL handling — — Recognizes GitHub, GitLab, Bitbucket, and Gist page URLs and rewrites them to raw-content endpoints before fetching
• Self-documenting — — Includes an internal://instructions resource and a get-help prompt so clients know how to use it
• HTTP mode — — Optionally serves over Streamable HTTP with host/origin validation, bearer or OAuth auth, rate limiting, health checks, and TLS

Setting it up

Installation goes through your MCP client rather than a global install: point it at args on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Superfetch is connected, these are the calls the assistant has available:

• Tools — The Tools tool exposed by this server
• Resources — The Resources tool exposed by this server
• Prompts — The Prompts tool exposed by this server

Configuration and credentials

You will need 8 environment variables: OAUTH_ISSUER_URL, OAUTH_AUTHORIZATION_URL, OAUTH_TOKEN_URL, OAUTH_REVOCATION_URL, OAUTH_REGISTRATION_URL, OAUTH_INTROSPECTION_URL, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET. 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.

• Node.js >= 24 - Docker (optional) — only needed if you want to run the container image

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• 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 superfetch mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Superfetch's toolset — Tools, Resources, Prompts — is a fair guide to whether it matches your workflow. It is maintained by j0hanz; 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.