Skip to main content
Glama
lachy3433

contextfetch-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CONTEXTFETCH_API_KEYNoYour API key. Unset or empty uses the free keyless tier.
CONTEXTFETCH_API_BASENoAPI base URL. Point it at your own engine if you self-host.https://api.contextfetch.dev

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
contextfetch_searchA

Search the web and get LLM-ready Markdown. Each result has its title, URL and only the passages relevant to the query (cross-encoder pruned context), so it costs far fewer tokens than raw pages. Use for current events, documentation, APIs, research and fact checking.

contextfetch_extract_urlA

Fetch a public web page (docs, articles, GitHub files, arXiv papers) as clean Markdown with tables preserved. Pass query to get only the passages relevant to it instead of the whole page.

contextfetch_find_similarA

Find pages similar to a given URL (alternatives, related docs, competing libraries), excluding the source domain. Returns titles, URLs and the most relevant passages as Markdown.

contextfetch_researchA

Research a question in one call, server-side: runs up to 5 web searches (sub-queries) concurrently, dedupes the pages by URL, ranks them all against the question with a cross-encoder and returns one Markdown evidence pack with numbered [n] sources and their query-pruned passages, quoted verbatim (no generated text). Costs 1 credit per sub-query. Pass your own sub_queries (distinct angles on the question) for better coverage. If omitted they are derived from query: the query itself, query + "documentation", and query + "benchmark" when it asks about speed, performance or comparisons, else query + "example" (a suffix the query already contains is skipped).

contextfetch_deep_researchA

Same as contextfetch_research (kept for existing setups): up to 3 sub-queries run server-side, sources deduped and ranked against the question, one Markdown evidence pack with numbered sources and query-pruned passages. Each sub-query is one search and costs 1 credit. You SHOULD pass your own sub_queries (up to 3 distinct angles on the question) for better coverage. If omitted they are derived from query: the query itself, query + "documentation", and query + "benchmark" when it asks about speed, performance or comparisons, else query + "example" (a suffix the query already contains is skipped).

contextfetch_answerA

Answer a question with passages quoted verbatim from the web, never generated: searches, scores every passage of the top pages with a cross-encoder and returns the best ones with [n] citations to their sources. Use it for quick factual lookups; the quotes may not fully answer an open-ended question. Costs 1 credit.

contextfetch_crawlA

Crawl one website from a start URL and get its pages as Markdown: same-site links only, up to max_depth hops (<= 3) and limit pages (<= 50), robots.txt obeyed. Pass query to rank the pages by relevance and return only their relevant passages. Costs 1 credit per page returned.

contextfetch_mapA

List a website's URLs without fetching its pages: its sitemaps (from robots.txt, else /sitemap.xml) plus the start page's links, same site only, up to limit (<= 5,000). Use it to find the right pages before contextfetch_extract_url or contextfetch_crawl. Costs 1 credit.

contextfetch_balanceA

Show the API key's remaining credits, daily burn rate (7-day average) and auto-reload settings, including the last auto-reload error if a payment failed. Needs CONTEXTFETCH_API_KEY; free. Check it before long jobs.

contextfetch_auto_reloadA

Turn auto-reload on or off, or change it: when credits drop below threshold, the saved card buys pack again, up to monthly_max_usd per month. Needs CONTEXTFETCH_API_KEY and a card saved at checkout. The monthly cap cannot be raised above $500 here.

contextfetch_get_free_keyA

Get a free ContextFetch API key with 2,500 searches (one per network, no sign-up). This session uses it right away; give it to your user so they can set CONTEXTFETCH_API_KEY to keep it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 11 tools

Disambiguation4/5

Most tools target clearly distinct operations (search, extract_url, crawl, map, find_similar, balance). The main overlap is contextfetch_research vs contextfetch_deep_research, which the description openly admits is essentially the same tool kept for backwards compatibility, plus some conceptual overlap among search/answer/research.

Naming Consistency4/5

All names use a consistent contextfetch_ prefix and snake_case, making the set predictable. The only deviation is that some are verb_noun (extract_url, find_similar, get_free_key) while others are bare verbs or nouns (search, answer, crawl, map, balance), but this is minor and readable.

Tool Count5/5

11 tools is well within the ideal 3-15 range for a web-context service. Each tool covers a distinct capability (fetch, crawl, search, research, discovery, billing), with only the redundant deep_research arguably not earning a slot.

Completeness5/5

The surface covers the full lifecycle for a web-context service: onboarding (get_free_key), discovery (map, find_similar), retrieval (extract_url, crawl, search), synthesis (research, answer) and account management (balance, auto_reload). No obvious dead ends for the stated purpose.