url-context-mcp
An MCP server that fetches web pages and extracts clean, AI-usable context from them, enabling tools for link discovery, content search, and integrated fetch-and-search operations.
README
url-context-mcp
An MCP (Model Context Protocol) server that fetches web pages and extracts clean, AI-usable context from them. Runs over stdio transport.
It's designed for AI agents that need to:
- Read a web page as clean markdown (no boilerplate, no nav/footer noise)
- Discover links on a page (with filters) before deciding what to fetch next
- Search pages for specific text/code without reading the whole thing
- Do all of the above in a single call
Tools
| Tool | What it does |
|---|---|
fetch_url |
Fetch a URL → readable article as markdown (or text/html/readable). Optional includeLinks=false, maxChars. |
extract_links |
Get all links from a URL or raw HTML. Optional regex filter, sameDomainOnly, limit. Resolves relative links correctly. |
search_content |
Regex search a URL's content; returns matches with surrounding context. |
fetch_and_search |
One-shot combo: returns content and links and search matches in a single call. The most token-efficient way to understand + navigate a page. |
fetch_image |
Fetch an image by URL (absolute or relative to a base page) and return it as base64 image content the model can see. Resolves relative URLs from page extraction (e.g. images/logo.png against the page that referenced it). Optional maxSizeKB guard (default 512 KB). |
All tools accept either a url (server fetches it) or raw html (you provide the markup), so they're composable with other fetchers too.
Installation (copy-paste into your MCP client config)
{
"mcpServers": {
"url-context": {
"command": "npx",
"args": ["-y", "url-context-mcp"]
}
}
}
That's it. npx -y downloads and runs the server on first use; no separate install step needed. Requires Node.js 18+.
Why it's the best design for an AI agent
- Readability-first: defaults to Mozilla Readability extraction so the agent gets the article, not the chrome. Reduces tokens and irrelevance.
- One-call combo:
fetch_and_searchreturns content + links + matches together — fewer round trips when an agent wants to "understand this page and find X on it". - Link discovery before prefetch:
extract_linkslets an agent survey a page's destinations and pick the right one to fetch, instead of guessing or fetching everything. - Regex search with context: agents can locate an error string, an API endpoint, a version number, etc. on a page with bounded context windows.
- No browser, no head: pure HTTP + jsdom. Fast, sandboxed, works anywhere Node runs. No Playwright/Chromium dependency bloat.
- Sane defaults + truncation:
maxChars,limit,maxMatcheskeep responses bounded so context windows don't blow up.
Local development
npm install
node index.js # run the stdio server
npm pack # build the publishable tarball
Changelog
1.2.0
- New tool:
fetch_image. Resolves an image URL (absolute, or relative to abaseUrl) and returns it as an MCPimagecontent block (base64 with amimeTypederived from the response Content-Type header, falling back to the URL extension). Lets the model actually see images found in pages marked up in markdown. OptionalmaxSizeKB(default 512 KB) protects the context window from oversized payloads. MIME fallback map covers png/jpg/jpeg/gif/webp/svg/bmp/avif/ico. - Server version bumps to 1.2; user-agent string updated accordingly.
1.1.0
- Preserve dropped headings in extracted content. Mozilla Readability
strips the page
<h1>/title from itscontenton minimal pages (e.g.example.com: the# Example Domainheading was never returned byfetch_url, andsearch_contenttherefore couldn't find "Example Domain"). We now detect headings present in the raw body but missing from Readability's cleaned HTML and re-prepend them, so the page title is always part of the returned markdown/text and is searchable. search_contentraw-HTML fallback. When a search of the converted (markdown/text) content finds zero matches and raw HTML is available, the tool re-runs the search against the stripped raw text as a safety net. The result flag notes when the fallback path was used ((raw-HTML fallback)in the header).- Misc: user-agent string bumped to
1.1.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.