keephaven-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEEPHAVEN_URL | Yes | The URL of the Keephaven box, e.g. http://keephaven-xxxx.local:8790 | |
| KEEPHAVEN_TOKEN | Yes | The agent token shown once when adding an agent in Keephaven's Settings > Agents |
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 |
|---|---|
| memory_statusA | Who you are on this Keephaven, whether you can write, and how much of your quota is used. |
| memory_listA | List the files in your memory, optionally under a folder prefix like 'people' or 'projects/keephaven'. |
| memory_readA | Read one file from your memory. Returns its text and an etag; pass the etag to memory_write to avoid overwriting a newer copy. |
| memory_writeA | Create or replace one file in your memory (UTF-8 text, up to 10 MB). Paths are plain segments of letters, digits, _ . - separated by '/'. journal/ is not writable here: use journal_append. |
| memory_deleteA | Delete one file from your memory on the box. Journal files can't be deleted. A paired backup box keeps what it already received. |
| journal_appendA | Append one entry to your append-only journal: what you did, decided, or learned. Nothing in the journal can be edited or deleted afterwards, so it's the record your future sessions can trust. |
| journal_readA | Read your most recent journal entries, oldest first. Use at the start of a session to pick up where you left off. |
| memory_searchA | Case-insensitive text search across your memory files and journal. Returns matching lines with file and line number. |
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 8 tools
Each tool targets a distinct resource-action pair: memory file operations, append-only journal operations, search, and status. The boundary between memory_write and journal_append is explicitly clarified, preventing likely misselection.
All tools follow a predictable resource_action pattern: memory_* for file memory and journal_* for journal operations. The convention is consistent and easy to infer.
Eight tools are well-scoped for a memory/filesystem server with an append-only journal. Each tool has a clear role without excessive fragmentation.
The set covers memory file CRUD (read/write/list/delete), identity and quota status, search across memory and journal, and append/read journal lifecycle. The append-only journal intentionally omits edit/delete operations, so the surface is complete for the stated domain.