kChat MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KCHAT_TOKEN | Yes | Your kChat token. Can be linked to a user via the API Token page or to a bot account via kChat Integrations. | |
| KCHAT_TEAM_NAME | Yes | Your kChat team unique name (e.g., 'your-team' from https://your-team.kchat.infomaniak.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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kchat_list_channelsB | List kChat public channels with pagination |
| kchat_post_messageC | Post a new message to a kChat channel |
| kchat_reply_to_threadC | Reply to a specific message thread in kChat |
| kchat_add_reactionC | Add a reaction emoji to a kChat message |
| kchat_get_channel_historyC | Get recent messages from a kChat channel |
| kchat_get_thread_repliesC | Get all replies in a kChat message thread |
| kchat_get_usersA | Get a list of all users in the kChat with their basic profile information |
| kchat_send_direct_messageB | Send a direct message to a kChat user by username |
| kchat_get_user_profileB | Get detailed profile information for a specific kChat user |
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 9 tools
Most tools map to distinct resource+action pairs (channels, history, threads, reactions, users). The closest overlaps are post_message vs reply_to_thread vs send_direct_message, and get_users vs get_user_profile, but the descriptions make the distinctions clear enough to select correctly.
Every tool follows the exact same kchat_ + verb_noun pattern (kchat_list_channels, kchat_post_message, kchat_get_user_profile). Prefixing with the service name is uniform and predictable across all nine tools.
Nine tools is well within the sweet spot for a chat/messaging server. Each tool earns its place by covering a distinct messaging primitive (channels, messages, threads, reactions, users, DMs).
The surface covers the core chat lifecycle: list channels, read history, post, reply, react, DM, and inspect users. Minor gaps remain—no edit/delete message, no remove reaction, no search, and no way to list existing DM conversations—but agents can work around these for most workflows.