Kagi Translate 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. Obtain one by emailing support@kagi.com. |
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 |
|---|---|
| translate_textB | Translate text between languages using Kagi Translate. |
| translate_urlC | Translate the content of a URL using Kagi Translate. |
| proofreadC | Proofread text with Kagi Translate. |
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 3 tools
Each tool has a clearly distinct purpose: proofreading text, translating text, and translating a URL's content. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (proofread, translate_text, translate_url) using lowercase with underscores, making them predictable.
Three tools is well-scoped for a translation/proofreading server. Each tool serves a necessary function without excess or deficiency.
The surface covers the core domain: text translation, URL translation, and proofreading. No obvious gaps given the stated purpose.