kagi-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KAGI_API_KEY | Yes | Your Kagi API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kagi_searchC | Perform web search using Kagi |
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 1 tool
Only one tool exists, so there is no possibility of confusion or overlap with other tools. The tool's purpose is clearly defined as performing a web search.
With a single tool, naming consistency is trivially satisfied. The name kagi_search follows a clear vendor_action pattern, though there is no other tool to compare it against.
A single tool for a search server is extremely thin. While a search-only server could be minimal, one tool provides very limited functionality and feels insufficient for a full-featured server.
The server only offers search, with no support for related operations like fetching search results by ID, saving searches, or accessing Kagi's other features. The surface is severely limited for a search-focused server.