url-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_urlA | Fetch a URL and return its main readable content as clean markdown by default (Readability extraction). Options: format=markdown|text|html|readable, includeLinks=false to strip hyperlinks, maxChars to truncate. Useful for reading a web page, understanding a code/docs page, or getting article content without boilerplate. |
| extract_linksA | Extract all hyperlinks from a URL (or raw HTML). Returns array of {href, text, title, section, isExternal, hash, type} grouped to dedupe. Great for discovering pages/anchors before fetching them. |
| search_contentA | Search the content of a URL (or raw HTML) and return matching snippet(s) with surrounding context and line numbers. Useful to find specific text/code/errors on a page without reading the whole thing. |
| fetch_and_searchA | One-shot combo: fetch a URL and simultaneously return BOTH the cleaned content AND its links AND any matching search snippets. Most efficient when you want to understand a page and also navigate/search it. Omit pattern/links as needed. |
| fetch_imageA | Fetch an image from a URL (absolute or relative to a base page) and return it as base64 image content that the model can see. Use when a page's markdown contains relative image URLs (e.g. |
) and you need to view the image. Optional compression can shrink oversized images to fit within maxSizeKB.Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct output (content, links, search snippets, combined result, or image). The combo tool fetch_and_search is explicitly labeled as a one-shot convenience, so there is no ambiguity about when to use it.
All tools use snake_case and start with a verb (fetch, extract, search). The only deviation is fetch_and_search, which uses a compound verb phrase rather than a strict verb_noun pattern, but it is still readable and consistent in style.
Five tools is a well-scoped size for a URL context server. Each tool covers a distinct need without unnecessary overlap or bloat.
The set covers the core operations of fetching content, extracting links, searching within pages, retrieving images, and a combined mode. No obvious missing functionality for the stated purpose.