ChatAtlas-local
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHATATLAS_LOCAL_DB | No | Path to the ChatAtlas Local SQLite archive file. Defaults to ~/.chatatlas-local/chatatlas.db. The same location can be set with --db <file> or the CHATATLAS_LOCAL_DB setting. | ~/.chatatlas-local/chatatlas.db |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_chatsA | Find the user's saved conversations that mention something: chats holding every word of the query in the title or messages (each word also matches longer words it starts, accents ignored), title matches first, then newest, with the best-matching message quoted. Each result has the chat's id for read_chat. |
| list_chatsA | Browse the user's saved conversations, newest first, by platform, date, words in the title or tag. Each line has the chat's id for read_chat. |
| read_chatA | Read one saved conversation, message by message, numbered from 1. Long chats come a page at a time: carry on with from_message. A very long single message comes in parts: carry on with part. |
| recent_topicsB | What the user talked about with their AIs over a stretch of days: how many chats on each platform, the tags that come up most, and the chats' titles week by week. |
| archive_overviewA | What the archive holds: how many chats from each platform, the dates they cover, the tags in use and when it was last imported. |
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 5 tools
Each tool has a distinct primary purpose: aggregate overview, content search, filtered browsing, single-chat reading, and recent topic summarization. The main overlap is between search_chats and list_chats, since both can find chats by title words, but their descriptions clarify that search also scans message content while list is for browsing with metadata filters.
The names use consistent snake_case and readable vocabulary, but the convention is mixed: search_chats, list_chats, and read_chat are verb_noun, while archive_overview and recent_topics are noun phrases. This is still understandable but not a predictable single pattern.
Five tools is well-scoped for a local chat archive: overview, search, browse, read, and recent-topic summarization. Each tool covers a distinct workflow and none feels redundant or extraneous.
The surface covers the core read-only lifecycle for saved conversations: orienting with overview/topics, finding chats, browsing, and reading messages with pagination. Minor gaps exist around archive management, such as import, export, or tag editing, but these may be intentionally out of scope.