Kagi MCP 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
Server capabilities have not been inspected yet.
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as performing web searches using Kagi, leaving no room for misselection.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'kagi_search' follows a clear verb_noun pattern, but consistency cannot be assessed across a set of one.
A single tool is too few for a server that appears to be focused on web search functionality, as it lacks complementary operations like summarization, filtering, or handling search results. This minimal scope feels incomplete for the domain.
The tool surface is severely incomplete for a web search domain, as it only provides raw search capability without tools for processing, refining, or managing search results. This creates significant gaps that will limit agent effectiveness.