kakaotalk-mcp-korea
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KAKAOTALK_LANG | No | Language of error messages: en, ko, ru or uz. | en |
| KAKAOTALK_APP_NAME | No | App name used for Accessibility lookups. | KakaoTalk |
| KAKAOTALK_LOG_LEVEL | No | Log level: debug, info, warn or error (logs go to stderr). | info |
| KAKAOTALK_SCRIPT_TIMEOUT_MS | No | Timeout for UI automation steps. | 15000 |
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 |
|---|---|
| kakao_list_chatsB | List chats ordered by last activity, with unread counts. |
| kakao_read_messagesA | Read recent messages. Pass a chat name (substring is fine) or chat id. since accepts 30m, 12h or 7d. |
| kakao_search_messagesB | Search message text across all chats. |
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
list_chats, read_messages, and search_messages have reasonably distinct purposes: enumerating chats, reading one chat's history, and searching text globally. The only mild overlap is that read_messages and search_messages both return message content, but the input models (chat-scoped vs global query) differentiate them.
All three tools use the same kakao_ prefix followed by a verb_noun pattern (list_chats, read_messages, search_messages). Perfectly predictable and readable.
Three tools is on the thin side but coherent for a focused read/search scope. Each tool earns its place, though the surface feels minimal for a full chat client.
The surface is read-only: there is no send/reply, mark-as-read, get-chat-details, or participant listing. For a messaging domain, the inability to write or manage messages is a significant gap that will block common agent tasks.