KiMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SK_APP_KEY | No | Your SK App key | |
| NAVER_CLIENT_ID | No | Your Naver client ID | |
| KAKAO_REST_API_KEY | No | Your Kakao REST API key | |
| NAVER_CLIENT_SECRET | No | Your Naver client secret |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_webpage_contentA | |
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 overlap or confusion between tools. The single tool has a clear, specific purpose.
The tool name follows a clear verb_noun pattern and is descriptive. However, with only one tool, there is not enough surface area to fully demonstrate naming consistency across a set.
A single tool feels too thin for a general-purpose server, even for a focused web-fetching utility. There is no room for alternative operations or related functionality.
For the stated purpose of fetching and stripping HTML from a webpage, the tool fully covers the core use case. Minor gaps exist, such as handling raw HTML or additional page metadata, but these are not obvious dead ends.