chatlab-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHATLAB_HOST | No | ChatLab listen host | 127.0.0.1 |
| CHATLAB_PORT | No | ChatLab HTTP API port | 3110 |
| CHATLAB_TOKEN | No | Bearer token passed to chatlab-cli and used for API calls | generated per MCP process |
| CHATLAB_CLI_BIN | No | Optional custom executable or script path | bundled chatlab-cli |
| CHATLAB_API_PORT | No | Fallback port variable if CHATLAB_PORT is not set | |
| CHATLAB_HEADLESS | No | Use --headless; set to false to serve the Web UI too | true |
| CHATLAB_AUTO_START | No | Start chatlab-cli automatically before API calls | true |
| CHATLAB_TIMEOUT_MS | No | HTTP request timeout | 30000 |
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 |
|---|---|
| chatlab_startB | Start chatlab-cli in headless HTTP API mode. Port defaults to CHATLAB_PORT or 3110. |
| chatlab_stopA | Stop the chatlab-cli child process started by this MCP server. |
| chatlab_statusA | Get local process state and ChatLab API status. |
| chatlab_list_sessionsB | List imported ChatLab sessions. |
| chatlab_get_sessionA | Get metadata for one imported ChatLab session. |
| chatlab_get_messagesC | Get paginated messages from a ChatLab session. |
| chatlab_get_membersC | List members in a ChatLab session. |
| chatlab_get_overviewC | Get overview stats for a ChatLab session. |
| chatlab_execute_sqlB | Execute readonly SQL against a ChatLab session database. |
| chatlab_export_sessionB | Export one ChatLab session as ChatLab-format JSON. |
| chatlab_import_sessionC | Import a ChatLab-format JSON payload into a session ID. |
| chatlab_requestA | Call any ChatLab HTTP API endpoint. Use this for endpoints not covered by dedicated tools. |
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 12 tools
Each tool targets a distinct action—SQL execution, session export/import, listing, metadata retrieval, members, messages, overview, generic API call, and process management. No two tools have overlapping functionality, making it easy for an agent to select the correct one.
All tools use the 'chatlab_' prefix and snake_case. Most follow a verb_noun pattern (e.g., execute_sql, list_sessions), but 'chatlab_request' uses a noun as the verb, and the process commands (start, stop, status) omit a noun, breaking the pattern slightly.
With 12 tools, the set is well-scoped for managing ChatLab sessions: it covers session CRUD, data retrieval, SQL execution, process lifecycle, and a generic fallback. Neither too few nor too many for the domain.
The tools cover core session management (list, get, import, export, execute SQL, view members/messages/overview) and process control. Missing explicit update/delete operations, but the generic 'chatlab_request' tool can be used to fill gaps, preventing agent dead ends.