kagi-kan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KAGI_SESSION_TOKEN | No | Your Kagi session token for authentication |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kagi_search_fetchA | Fetch web results based on one or more queries using the Kagi.com web search engine. Use for general search and when the user explicitly tells you to 'fetch' results/information. Results are from all queries given. They are numbered continuously, so that a user may be able to refer to a result by a specific number. Supports optional limit parameter to control results per query. |
| kagi_summarizerA | Summarize content from a URL using the Kagi.com Summarizer API. The Summarizer can summarize any document type (text webpage, video, audio, etc.) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve entirely different purposes: one for fetching web search results, the other for summarizing content from a URL. There is no overlap or ambiguity.
Both tools use a consistent 'kagi_<action>' pattern (kagi_search_fetch and kagi_summarizer), making the naming predictable and easy to follow.
With only two tools, the server is minimal but still covers its core capabilities of search and summarization. Each tool earns its place, though the count is slightly below the typical 3-15 range.
The tool set covers the fundamental operations for the server's purpose: searching the web and summarizing content. Minor gaps like additional result filtering or multiple summary modes exist, but the core workflow is complete.