MCP100 verdict
Recommended first-party search MCP when you want a small, focused search-and-extraction surface backed by Kagi and can use a Kagi API key.
MCP100 Assessment
Editorial verdict
Reviewed September 11, 2026
Task Fit
Mapped
Web search and research
Trust
Reviewed
A dated editorial review is published on the MCP detail page.
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
No MCP-specific repository metric is stored
No MCP-specific package metric is stored
Stars observation date unavailable · Downloads observation date unavailable
Publisher activity observed September 11, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed September 11, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
No sufficient client-specific setup evidence has been stored from the publisher or client documentation.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-09-11T00:00:00.000Z
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
uvx kagimcpCapability
Recommended first-party search MCP when you want a small, focused search-and-extraction surface backed by Kagi and can use a Kagi API key.
Search the web with Kagi and return fetched/ranked results.
Extract readable content from one or more URLs.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
Reviewed access
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
Related reviewed MCPs
Search, scrape, crawl, and extract web content through Firecrawl.
Choose this instead if
Choose Firecrawl MCP instead if scraping and extracting public web pages.
Search, scrape, crawl, and extract web content through Firecrawl.
Search Hugging Face Hub resources and use explicitly enabled Jobs, sandboxes, and community Space tools.
Choose this instead if
Choose Hugging Face MCP instead if searching models, datasets, Spaces, papers, and Hugging Face documentation.
Search Hugging Face Hub resources and use explicitly enabled Jobs, sandboxes, and community Space tools.
Connect compatible AI clients to Perplexity's documented MCP capabilities.
Choose this instead if
Choose Perplexity MCP instead if current web search and cited question answering with Perplexity APIs.
Recommended first-party Perplexity MCP for real-time search, question answering, reasoning, and deep research through a small four-tool surface.
Kagi Inc. is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
An MCP server backed by the Kagi API. It exposes search and extraction tools to MCP-compatible clients.
kagi_search_fetch - web, news, videos, podcasts, and image search with optional page extracts, filters, and Kagi lenses.kagi_extract - fetch a page's full content as markdown.Note: The previous
kagi_fastgptandkagi_summarizertools have been removed. Both are planned to return in a future release.
We run a hosted MCP server at https://mcp.kagi.com/mcp — no install required. Point any HTTP-capable MCP client at it and authenticate with your Kagi API key.
OAuth2 isn't supported yet (it's on our roadmap), so for now grab your API key from the dashboard and pass it via Bearer HTTP authentication.
Example with Claude Code:
claude mcp add kagi https://mcp.kagi.com/mcp --transport http --header "Authorization: Bearer $(read -sp 'API key: ' k; echo $k)" --scope user
Prefer to run it yourself? See Client Setup for the local uvx install, or Self-Hosting to host the HTTP server on your own infrastructure.
KAGI_API_KEY.uv for the recommended uvx install path.Install uv:
curl -LsSf https://astral.sh/uv/install.sh | sh
Windows:
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Who was Time's 2024 person of the year?extract the full content of https://en.wikipedia.org/wiki/Model_Context_Protocol| Environment variable | Description |
|---|---|
KAGI_API_KEY | Required Kagi API key. |
FASTMCP_LOG_LEVEL | Logging level, for example ERROR. |
KAGI_SEARCH_TIMEOUT | Search timeout in seconds. Defaults to 10. |
KAGI_EXTRACT_TIMEOUT | Extract timeout in seconds. Defaults to 30. |
KAGI_MAX_RETRIES | Max retry attempts after the first request. Defaults to 2; set 0 to disable retries. |
KAGI_HIDDEN_PARAMS | Comma-separated search params to hide from the LLM-facing schema. |
Hideable search params:
workflow, extract_count, limit, include_domains, exclude_domains, time_relative, after, before, file_type, lens_id
Example:
KAGI_HIDDEN_PARAMS="extract_count,after,before,time_relative,include_domains,exclude_domains"
git clone https://github.com/kagisearch/kagimcp.git
cd kagimcp
uv sync
Run locally over stdio:
KAGI_API_KEY=<YOUR_API_KEY_HERE> uv run kagimcp
Run with streamable HTTP transport:
KAGI_API_KEY=<YOUR_API_KEY_HERE> uv run kagimcp --http --host 0.0.0.0 --port 8000
HTTP mode is multi-tenant: each request supplies its API key via the
Authorization: Bearer <key> header instead of a server-wide env var, so one
instance can serve multiple users. The repo ships a Dockerfile that installs a pinned kagimcp from PyPI and
runs it in HTTP mode. The container respects $PORT so it works on any
platform that injects one (Railway, Render, Cloud Run, Fly.io, etc.).
Build and run locally:
docker build -t kagimcp-hosted .
docker run --rm -p 8000:8000 kagimcp-hosted
Smoke test:
curl -sL http://127.0.0.1:8000/mcp -X POST \
-H "authorization: Bearer $KAGI_API_KEY" \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
To bump the version in production, edit the pin in the Dockerfile and redeploy.
Inspect the published package:
npx @modelcontextprotocol/inspector uvx kagimcp
Inspect a local checkout:
npx @modelcontextprotocol/inspector uv --directory /ABSOLUTE/PATH/TO/kagimcp run kagimcp
The inspector is usually available at http://localhost:5173.
If using a prerelease build, the same installation instructions apply, but use uvx --prerelease allow --from kagimcp==1.0.0rc2 kagimcp instead of uvx kagimcp (replace 1.0.0rc2 with whatever version you're wanting to install).
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Publisher-documented clients
These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.
codex mcp add kagi --env KAGI_API_KEY=<YOUR_API_KEY_HERE> -- uvx kagimcp
Codex writes MCP configuration to ~/.codex/config.toml.
Install uv first.
MacOS/Linux:
curl -LsSf https://astral.sh/uv/install.sh | sh
Windows:
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Then in your Claude Desktop config (found through Settings -> Developer -> Edit Config):
{
"mcpServers": {
"kagi": {
"command": "uvx",
"args": ["kagimcp"],
"env": {
"KAGI_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
claude mcp add kagi -e KAGI_API_KEY="YOUR_API_KEY_HERE" -- uvx kagimcp
npx -y @smithery/cli install kagimcp --client claude
Add to your Kiro MCP config file (~/.kiro/settings/mcp.json for global, or .kiro/settings/mcp.json for project-scoped) using the same mcpServers JSON as Claude Desktop. See the Kiro MCP documentation for more details.
Edit the OpenCode configuration file in ~/.config/opencode/opencode.json and add the following:
{
"mcp": {
"kagi": {
"type": "local",
"command": ["uvx", "kagimcp"],
"enabled": true,
"environment": {
"KAGI_API_KEY": "<YOUR_API_KEY_HERE>"
}
}
}
}