Kagi MCP sends search queries, page URLs, filters, date ranges, lens IDs, and extraction requests to the Kagi API., Search and extraction calls can consume Kagi API quota or create API costs, especially when using high limits or inline page extraction., The `kagi_extract` tool fetches public page content as markdown; do not ask it to retrieve private, paywalled, or terms-restricted content unless you have permission., In HTTP mode, clients provide Kagi API keys through bearer tokens; expose the endpoint only behind trusted transport, access controls, and log redaction., The server supports configurable timeouts, retries, and hidden search parameters; tune these before giving broad agent access to current-web workflows.
Privacy notes
Kagi receives search queries, requested URLs, search filters, result domains, lens IDs, extraction targets, API keys, and request metadata., MCP clients and logs may store user questions, result snippets, extracted markdown, trace IDs, and error bodies returned by the Kagi API., Hosted HTTP deployments can process keys for multiple users; avoid server, proxy, and platform logs that record `Authorization` headers., Extracted pages may include personal data, copyrighted text, internal URLs, or sensitive context if the user provides those URLs.
Author
Kagi Search
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes, network access.
5 areas
SafetyNetwork accessKagi MCP sends search queries, page URLs, filters, date ranges, lens IDs, and extraction requests to the Kagi API.
SafetyGeneralSearch and extraction calls can consume Kagi API quota or create API costs, especially when using high limits or inline page extraction.
SafetyPermissions & scopesThe `kagi_extract` tool fetches public page content as markdown; do not ask it to retrieve private, paywalled, or terms-restricted content unless you have permission.
SafetyCredentials & tokensIn HTTP mode, clients provide Kagi API keys through bearer tokens; expose the endpoint only behind trusted transport, access controls, and log redaction.
SafetyGeneralThe server supports configurable timeouts, retries, and hidden search parameters; tune these before giving broad agent access to current-web workflows.
PrivacyCredentials & tokensKagi receives search queries, requested URLs, search filters, result domains, lens IDs, extraction targets, API keys, and request metadata.
PrivacyData retentionMCP clients and logs may store user questions, result snippets, extracted markdown, trace IDs, and error bodies returned by the Kagi API.
PrivacyPermissions & scopesHosted HTTP deployments can process keys for multiple users; avoid server, proxy, and platform logs that record `Authorization` headers.
PrivacyGeneralExtracted pages may include personal data, copyrighted text, internal URLs, or sensitive context if the user provides those URLs.
Disclosure: MIT-licensed official Kagi MCP server published as the `kagimcp` Python package. This entry is distinct from no-key public web search tools and research agents because it uses the Kagi Search and Extract APIs directly.
Safety notes
Kagi MCP sends search queries, page URLs, filters, date ranges, lens IDs, and extraction requests to the Kagi API.
Search and extraction calls can consume Kagi API quota or create API costs, especially when using high limits or inline page extraction.
The `kagi_extract` tool fetches public page content as markdown; do not ask it to retrieve private, paywalled, or terms-restricted content unless you have permission.
In HTTP mode, clients provide Kagi API keys through bearer tokens; expose the endpoint only behind trusted transport, access controls, and log redaction.
The server supports configurable timeouts, retries, and hidden search parameters; tune these before giving broad agent access to current-web workflows.
Privacy notes
Kagi receives search queries, requested URLs, search filters, result domains, lens IDs, extraction targets, API keys, and request metadata.
MCP clients and logs may store user questions, result snippets, extracted markdown, trace IDs, and error bodies returned by the Kagi API.
Hosted HTTP deployments can process keys for multiple users; avoid server, proxy, and platform logs that record `Authorization` headers.
Extracted pages may include personal data, copyrighted text, internal URLs, or sensitive context if the user provides those URLs.
Prerequisites
Python 3.12 and uv for the recommended `uvx kagimcp` install path.
A Kagi API key stored in `KAGI_API_KEY` for local stdio use.
Review of Kagi API billing, rate limits, search workflows, extraction behavior, and any client logs that may capture query text.
Optional HTTP deployment review if exposing the streamable HTTP transport to multiple users.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
beginner
Tool listing metadata
Disclosure
MIT-licensed official Kagi MCP server published as the `kagimcp` Python package. This entry is distinct from no-key public web search tools and research agents because it uses the Kagi Search and Extract APIs directly.
Kagi MCP Server connects Claude and other MCP clients to Kagi's Search and
Extract APIs. It exposes kagi_search_fetch for web, news, video, podcast, and
image searches with optional filters, date limits, domains, file types, lenses,
and inline page extracts. It also exposes kagi_extract for retrieving a
public page as markdown.
Use it when a Claude workflow needs current web results or page extraction from
a Kagi-backed source instead of a generic scraping stack. For local desktop
usage, run it over stdio with KAGI_API_KEY; for shared deployments, review the
HTTP bearer-token flow and logging behavior before exposing the endpoint.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, PyPI metadata, license, package metadata, server implementation, and
Dockerfile for current setup and operating details.
Features
Search the web through Kagi's general search workflow.
Search news, videos, podcasts, and images with workflow-specific result types.
Fetch inline markdown extracts for top search results.
Extract a specific HTTPS page as markdown through the Kagi Extract API.
Restrict searches by included or excluded domains.
Filter by relative time, explicit date bounds, file type, or Kagi lens.
Hide selected optional search parameters from the LLM-facing schema with
KAGI_HIDDEN_PARAMS.
Configure API retries, search timeout, extract timeout, and log level.
Run over local stdio for desktop clients or streamable HTTP for hosted use.
Use bearer tokens per request in HTTP mode so one hosted instance can serve
multiple Kagi users without a shared server-wide key.
Claude Code can add the same server from the command line:
claude mcp add kagi -e KAGI_API_KEY="YOUR_KAGI_API_KEY" -- uvx kagimcp
For local development from a checkout:
KAGI_API_KEY=YOUR_KAGI_API_KEY uv run kagimcp
For streamable HTTP mode:
KAGI_API_KEY=YOUR_KAGI_API_KEY uv run kagimcp --http --host 0.0.0.0 --port 8000
Use Cases
Give Claude current web results without leaving the MCP client workflow.
Search recent news or technical documentation with explicit domain and date
filters.
Fetch markdown extracts from public pages before summarizing or comparing
sources.
Use Kagi lenses to constrain research to curated source sets.
Add web, news, video, podcast, or image discovery to coding, writing, or
research agents.
Host a streamable HTTP endpoint for a controlled team environment where each
user supplies their own Kagi API key.
Safety and Privacy
Kagi MCP is a networked search and extraction server. Treat every query, URL,
filter, lens ID, and extracted result as data sent to both the MCP client and
Kagi's API. Avoid sending private URLs, credentials, internal tickets, customer
names, or confidential research topics unless that use is approved for your
Kagi account and model provider workflow.
When using HTTP mode, protect the endpoint like an API service. The server
accepts bearer tokens and passes them to Kagi, so reverse proxies, platform
logs, debugging middleware, and error reporting must not record authorization
headers.
Duplicate Notes
Existing catalog entries cover no-key public search, scraping/crawling tools,
and research agents. This entry covers the official kagisearch/kagimcp
repository and kagimcp package, which specifically wrap the Kagi Search and
Extract APIs for MCP clients.
Show that Kagi MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/kagi-mcp-server)
How it compares
Kagi MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server that unifies web search, AI answer, GitHub search, and web extraction providers including Tavily, Brave, Kagi, Exa, Linkup, Firecrawl, and GitHub behind four consolidated tools.
No-key multi-engine MCP server, CLI, and local daemon for web search and public web content retrieval across engines such as Bing, DuckDuckGo, Brave, Exa, Baidu, CSDN, Juejin, Startpage, and Sogou.
Local-first MCP server for web scraping, crawling, URL mapping, batch extraction, structured extraction, summarization, diffing, brand extraction, and optional hosted API fallback for bot-protected pages.
✓Kagi MCP sends search queries, page URLs, filters, date ranges, lens IDs, and extraction requests to the Kagi API.
Search and extraction calls can consume Kagi API quota or create API costs, especially when using high limits or inline page extraction.
The `kagi_extract` tool fetches public page content as markdown; do not ask it to retrieve private, paywalled, or terms-restricted content unless you have permission.
In HTTP mode, clients provide Kagi API keys through bearer tokens; expose the endpoint only behind trusted transport, access controls, and log redaction.
The server supports configurable timeouts, retries, and hidden search parameters; tune these before giving broad agent access to current-web workflows.
✓Omnisearch MCP Server can query multiple third-party search, AI answer, GitHub search, extraction, scraping, crawling, summarization, and content-processing providers.
Firecrawl crawl, scrape, map, extract, and action modes can interact with websites and may trigger robots.txt, TOS, rate-limit, or authentication concerns.
GitHub search depends on the configured token scope and can reveal private code, repositories, users, or organization metadata when a broad token is used.
Large result mode can write response content to files; review where those files are stored before using it with private or regulated data.
Require confirmation before crawling sites, extracting private URLs, using authenticated providers on sensitive targets, or running broad GitHub searches against private organizations.
✓open-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets.
Search and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections.
Respect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting.
The optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API.
Proxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately.
Leave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted.
✓WebClaw MCP Server can scrape one URL, crawl same-origin links, map URLs, batch multiple URLs, extract structured data, summarize pages, compare snapshots, and extract brand metadata.
Scraping, crawling, search, research, and hosted fallback can trigger target-site rate limits, bot protections, legal restrictions, or terms-of-service limits.
The server validates public HTTP URLs and rejects private or internal destinations, but operators should still avoid fetching internal, secret, customer-specific, or credential-bearing URLs.
Cookie-bearing requests, proxies, and browser profiles can expose authenticated sessions or route traffic through external infrastructure.
Setting `WEBCLAW_API_KEY` enables hosted API fallback, which can send target URLs and page context to the WebClaw service.
Structured extraction and summarization may use configured LLM providers; review provider data handling before enabling those tools with sensitive pages.
Privacy notes
✓Kagi receives search queries, requested URLs, search filters, result domains, lens IDs, extraction targets, API keys, and request metadata.
MCP clients and logs may store user questions, result snippets, extracted markdown, trace IDs, and error bodies returned by the Kagi API.
Hosted HTTP deployments can process keys for multiple users; avoid server, proxy, and platform logs that record `Authorization` headers.
Extracted pages may include personal data, copyrighted text, internal URLs, or sensitive context if the user provides those URLs.
✓Provider API keys, GitHub tokens, search queries, URLs, extracted page content, crawled site maps, scraped text, summaries, AI answers, GitHub search results, and large-result files can be exposed to the MCP client.
Search and extraction providers may log queries, URLs, source content, account identifiers, usage metadata, and generated responses according to their own policies.
Web extraction can capture personal data, paywalled content, internal URLs, or proprietary documents if supplied by the user or available to an authenticated provider.
GitHub search output may include repository names, code snippets, file paths, commit metadata, and organization details.
Keep provider credentials in local MCP configuration only, and avoid sharing transcripts that contain private queries, URLs, source text, or tokens.
✓Search queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context.
Live search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers.
Playwright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages.
The project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs.
Redact sensitive search terms and downloaded page content before sharing transcripts or logs.
✓URLs, fetched page content, crawl results, extracted structured data, snapshots, brand metadata, cookies, proxy settings, API keys, and LLM prompts can be exposed to the MCP client.
Crawled pages may include personal data, customer content, non-public links, access tokens embedded in URLs, or site-specific identifiers.
Diff snapshots and exported JSON can preserve page content longer than expected; store and delete them according to the workflow's retention needs.
Hosted fallback, proxy providers, search/research APIs, and LLM providers may observe target URLs, headers, cookies, prompts, and extracted content when enabled.
Redact sensitive URLs and extracted data before sharing MCP transcripts, crawl results, logs, or generated RAG context.
Prerequisites
Python 3.12 and uv for the recommended `uvx kagimcp` install path.
A Kagi API key stored in `KAGI_API_KEY` for local stdio use.
Review of Kagi API billing, rate limits, search workflows, extraction behavior, and any client logs that may capture query text.
Optional HTTP deployment review if exposing the streamable HTTP transport to multiple users.
Node.js 22 or newer for the published npm package.
At least one provider API key for Tavily, Kagi, Brave Search, GitHub, Exa, Linkup, or Firecrawl.
Optional `FIRECRAWL_BASE_URL` when using a self-hosted Firecrawl instance.
Optional `OMNISEARCH_LARGE_RESULT_MODE` choice for file or inline handling of large results.
Node.js 18 or newer for the published npm package.
Review of search-engine terms, scraping limits, rate limits, and allowed use for the target websites.
Optional proxy configuration only when live search or fetch traffic must route through an approved proxy.
Optional Playwright or browser endpoint setup only when request-based search/fetch is insufficient.
Node.js for the `create-webclaw` installer, or Rust/Cargo when building the MCP binary from source.
Review of AGPL-3.0 obligations before redistributing or operating modified server versions.
Review of target-site terms, robots expectations, rate limits, and scraping permissions.
Optional `WEBCLAW_API_KEY` only when hosted API fallback is acceptable for bot-protected or JavaScript-heavy pages.