Kagi MCP Server vs MCP Everything Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Kagi MCP Server MCP Servers	MCP Everything Server MCP Servers
Tagline	Official Kagi Search MCP server: search and extract the web from any MCP-compatible agent.	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
Category	MCP Servers	MCP Servers
Pricing	Paid· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month	Free· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
Model	—	—
Editorial score	—	—
Use cases	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 client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
Pros	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.	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
Cons	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	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
Website	github.com	github.com

Pick Kagi MCP Server if

✅ 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

Pick MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

Compare a different pair →