agtmem-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGTMEM_HOME | No | Optional path to the memory store directory. Defaults to ~/.agtmem. | ~/.agtmem |
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 |
|---|---|
| agtmem_searchA | Search long-term memory (hybrid FTS5 + trigram, RRF-merged). Returns short snippets with ids. Superseded notes are excluded. Use this first when resuming work on a project. |
| agtmem_readA | Read one note in full by id. Bounded by max_tokens. |
| agtmem_writeA | Create or update a note. Use type='decision' for choices and their rationale, 'fact' for durable truths, 'project' for project overviews, 'candidate' for unconfirmed guesses. Pass supersedes= to replace an outdated note — it is kept but marked superseded. |
| agtmem_appendA | Append a dated section to an existing note. Safe under concurrency. |
| agtmem_indexA | Rebuild the search index from the Markdown files. Always safe: the index is a cache and deleting it loses nothing. If |
| agtmem_bugA | Record a bug with the three parts that make it reusable: symptom, root cause, fix. Call this after solving anything non-obvious. |
| agtmem_candidatesB | List unconfirmed notes (type='candidate') — inferences the agent made that a human has not validated. Pass promote= to accept one. |
| agtmem_findA | Look up a symbol (function, class, method) in the codebase map and get file:line back. Cheaper and more precise than grepping or reading whole files. |
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 has a distinct primary role: search/read/write/append cover note lifecycle, while index/bug/candidates/find are specialized. The only mild overlap is between agtmem_search and agtmem_find, but their different targets (notes vs. code symbols) are clearly explained.
All tools share the agtmem_ prefix and use lowercase snake_case, giving a predictable surface. Most names are verbs (search, read, append, write, index, find), but 'bug' and 'candidates' are nouns, which is a slight deviation from the verb-action pattern.
Eight tools is well-scoped for a memory server: core note operations, search, maintenance, and specialized record types are each covered without redundancy. The count feels appropriate and not bloated.
The surface covers create, read, update, search, append, and supersede, which is solid for a memory store. There is no explicit delete or general list-all operation, but superseding and search compensate for most practical workflows.