kimi-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOONSHOT_API_KEY | Yes | Kimi API Key (required). API Key is only read from the environment variable MOONSHOT_API_KEY. You can also set it as a system environment variable instead of putting it in the config. | |
| MOONSHOT_BASE_URL | No | API base URL, used for proxy compatibility or testing. | https://api.moonshot.cn/v1 |
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 |
|---|---|
| kimi_searchA | Search the web with Kimi Search Basic. Returns titles, URLs, snippets, dates, and source authority. Keep include_content=false for an overview, then use kimi_fetch on selected URLs, or set it to true when full page text is needed. |
| kimi_search_proA | Search the web with Kimi Search Pro. Returns relevant page excerpts ranked by relevance, with source URLs and authority. Best for web QA, RAG, research, and reports. Supports site and publication-date filters. |
| kimi_fetchA | Fetch a single HTTP/HTTPS web page with Kimi and return its title and Markdown content. Use after kimi_search to read a specific URL. Subject to site availability, access controls, and Kimi security policy. |
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
kimi_fetch is clearly distinct from the two search tools. kimi_search and kimi_search_pro overlap heavily as web search operations, though the descriptions differentiate basic overview results from relevance-ranked excerpt results with filters.
All tools use a consistent kimi_ prefix with snake_case action names: kimi_search, kimi_search_pro, and kimi_fetch. The naming is predictable and easy to map to the intended operation.
Three tools are well-scoped for a web search and page-fetching server: two search modes plus a fetch operation. No unnecessary tools are present for the apparent purpose.
The server covers web search, advanced search, and single-page fetching, which supports the core search-and-read workflow. A batch fetch or multi-URL operation is missing, but agents can work around this by calling kimi_fetch per URL.