Kagi MCP Server vs MCP Fetch Server

Kagi MCP Server

MCP Servers

MCP Fetch Server

MCP Servers

Tagline

Kagi MCP Server

Official Kagi Search MCP server: search and extract the web from any MCP-compatible agent.

MCP Fetch Server

Official Model Context Protocol reference server that lets any MCP-compatible LLM fetch web pages and read them as clean markdown.

Pricing

Kagi MCP Server

Paid· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month

MCP Fetch Server

Free· Free and open source (MIT License). No hosted tier; you run it locally via uvx, pip, or Docker.

Lowest paid tier

Kagi MCP Server

$4 USD per user/month · Team

captured 2026-10-27

MCP Fetch Server

—

API

Kagi MCP Server

Yes

MCP Fetch Server

Not listed

Open source

Kagi MCP Server

Yes · MIT

MCP Fetch Server

Yes · NOASSERTION

GitHub stars

Kagi MCP Server

552

checked 2026-10-29

MCP Fetch Server

91,651

checked 2026-10-29

Last GitHub push

Kagi MCP Server

2026-10-28

MCP Fetch Server

2026-10-29

First commit

Kagi MCP Server

2024-12

MCP Fetch Server

2024-11

Package downloads (30 d)

Kagi MCP Server

—

MCP Fetch Server

175,042 · pypi mcp-server-git

checked 2026-10-15

Best for

Kagi MCP Server

Engineers using Claude Code, Claude Desktop, or other MCP clients who already pay for Kagi and want their agent to search and read the web through Kagi's cleaner index instead of a generic SERP API.

MCP Fetch Server

Developers wiring MCP-compatible LLMs (Claude Desktop, Claude Code, Cursor, VS Code) into everyday workflows that need clean, chunkable web reads — docs, READMEs, changelogs, articles.

Not for

Kagi MCP Server

Hobbyists who want a free web-search MCP, or teams that need summarizer/FastGPT tools today, or shops that require an on-prem search stack with no third-party API dependency.

MCP Fetch Server

Teams that need JavaScript-rendered pages, Cloudflare-gated sites, structured extraction, or crawling at scale — reach for Firecrawl-MCP or a Playwright-based server instead.

Editorial score

Kagi MCP Server

—

MCP Fetch Server

—

Use cases

Kagi MCP Server

agent web search groundingClaude Code documentation lookupdeep-research pipelinesURL to Markdown extraction for RAGnews and video search from an LLMKagi lens-scoped queries in agentscitation gathering for research assistantscoding agent error-message lookups

MCP Fetch Server

Reading documentation pages inside Claude DesktopGrabbing a GitHub README before scaffolding a projectSummarising a long article for a chat agentChecking a package changelog during code reviewAnswering questions from a linked spec section by sectionFeeding a URL into an MCP-driven research agentPulling clean markdown for a note-taking workflowVerifying a citation URL inside an editorial pipeline

Pros

Kagi MCP Server

• Official, first-party MCP server maintained by Kagi (not a community wrapper)
• Two clean tools that cover the 90% agent case: search and full-page Markdown extraction
• Both hosted (mcp.kagi.com) and local (uvx/Docker) deployment modes
• Documented setup recipes for Claude Desktop, Claude Code, Codex CLI, Kiro, OpenCode, Smithery
• MIT-licensed Python code, easy to fork or audit
• Rides Kagi's ad-free, spam-de-boosted index rather than generic SERP APIs
• Supports Kagi lenses and filters so agents can scope searches to news, docs, etc.

MCP Fetch Server

• Official reference implementation maintained in the modelcontextprotocol/servers repo — tracks the spec and won't rot behind third-party churn.
• Zero-install path via `uvx mcp-server-fetch`; Docker image and pip package also available for sandboxed or reproducible setups.
• HTML-to-markdown conversion produces context-window-friendly output instead of raw tag soup.
• `max_length` + `start_index` let a model chunk through long pages without blowing its context.
• Optional Node.js fallback swaps in a more robust HTML simplifier when present.
• First-class configuration for User-Agent, robots.txt obedience, and outbound proxy — practical knobs for real-world scraping etiquette.
• Works out of the box with every major MCP client (Claude Desktop, Claude Code, VS Code, Cursor, Zed, Continue).

Cons

Kagi MCP Server

• Requires a paid Kagi API key with pay-per-use billing; not usable free
• FastGPT and Universal Summarizer tools are currently absent (rewrite in progress)
• Python + uv toolchain assumption raises the bar vs. a single-binary MCP server
• Small surface area: no built-in caching, batching, or spend controls beyond Kagi's invoice cap
• Hosted endpoint means your queries and Bearer token traverse Kagi infra, not a concern for everyone but worth noting for regulated workloads

MCP Fetch Server

• No JavaScript rendering — SPAs, Cloudflare-challenged pages, and content loaded after DOMContentLoaded come back empty or as a shell.
• No built-in anti-bot handling; sites that block plain HTTP clients (many news sites, LinkedIn, X) will 403.
• Security caveat called out in the README: the server can reach local/internal IPs, so it is a genuine SSRF risk if exposed to an untrusted model or user.
• Single tool, single verb — for crawling, sitemap walks, or extracting structured data you need a heavier server like Firecrawl-MCP or a Playwright-based one.
• Truncation defaults to 5,000 characters; models that don't understand `start_index` can silently miss content below the fold.

Website

Kagi MCP Server

github.com

MCP Fetch Server

github.com

Editorial score: rule-based, 0–10, from AI-assisted profile inputs (see /methodology) — not a user rating; “—” means unscored. “Not listed” means we have no record of it, not that it is absent. GitHub figures and prices carry the date they were checked or captured; prices are shown as published, unconverted.