Skip to main content
Glama
kimi-sessions
by KekcuHa

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KIMI_CODE_HOMENoKimi Code home directory, respected when locating `server.token`.
KIMI_SESSION_MCP_TOKENNoExplicit token to use instead of reading the token from a file.
KIMI_SESSION_MCP_BASE_URLNoAPI address for the local `kimi web` REST API. Default is `http://127.0.0.1:58627`.http://127.0.0.1:58627
KIMI_SESSION_MCP_TOKEN_PATHNoAlternative path to the token file.
KIMI_SESSION_MCP_HTTP_TIMEOUT_MSNoREST request timeout in milliseconds. Default is `15000`.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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ListAgentsB

List unarchived Kimi Code sessions visible to the local server. Address sessions by exact name or session_ ID. The list can include cold sessions that are not currently loaded.

SendMessageA

Send plain text to another Kimi Code session. The sender name or ID is required because stdio MCP does not identify the calling session. The message is queued by Kimi; steer=true also lets a running turn consume it immediately. No permissions are transferred.

GetMessagesA

Read recent text messages from a session, newest first. Useful for collecting another session's reply; it does not mark messages as read.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have distinct scopes: ListAgents enumerates sessions, SendMessage sends text to a session, and GetMessages reads messages from a session. There is no meaningful overlap between listing sessions and reading or sending messages.

Naming Consistency5/5

All tool names follow a consistent PascalCase verb_noun pattern: ListAgents, SendMessage, GetMessages. The convention is predictable and easy to scan.

Tool Count5/5

Three tools is the right minimal surface for session discovery, sending, and reading. Each tool earns its place without redundant operations.

Completeness4/5

The core messaging lifecycle is covered: discover sessions, send messages, and read recent messages. Minor gaps exist around message read-state and session archiving/status, but agents can still work around them.