locus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTMCP_HOST | No | Host for SSE transport. Required when using --transport sse. Default is loopback. | 127.0.0.1 |
| LOCUS_PALACE | Yes | Path to the palace directory. Can also be provided via --palace command line argument. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_listA | List the palace index or the files within a room. Call without |
| memory_readA | Read a file from the palace.
|
| memory_writeA | Write content to a file within the palace.
Creates parent directories as needed. |
| memory_searchA | Full-text search across the palace (or a sub-path). Uses ripgrep (
|
| memory_batchA | Read multiple palace files in a single call.
Missing files, directories, and path-traversal violations are noted
inline and do not raise exceptions, so partial results are always
returned for valid calls. Raises Returns an empty string for an empty |
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 targets a distinct operation: batch read, list directory, single read, full-text search, and write. There is no overlap in functionality.
All tools follow a consistent 'memory_verb' pattern (batch, list, read, search, write), making it easy to infer purpose from name.
Five tools cover the core operations for a file-based memory system without being excessive or insufficient.
CRUD operations are covered except for delete/remove; a delete tool is missing, which could hinder agents needing to clean up files.