claude-crowed
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_readA | Fetch the full content of a specific memory. This is the only tool that returns content. Each read is tracked in the memory_accesses table. |
| memory_recallA | Search memory and return full content for the top results in a single call. Use this instead of memory_search + memory_read to reduce round trips. Returns two lists:
Call this at the START of every task AND whenever you hit unfamiliar territory mid-task. |
| memory_storeA | Store a new memory. Call this whenever you learn something worth remembering across sessions -- novel insights, decisions, findings, patterns, or debugging solutions. Title (max 150 chars) must be a complete, descriptive thought, not a label. Another instance of you should judge relevance from the title alone. Content max 1500 chars; split larger ideas into multiple memories. Source: manual, conversation, or auto. Rejects near-duplicates by default (threshold adjustable via |
| memory_updateA | Update an existing memory, creating a new version. The old version is preserved but removed from the search index. Returns the new version's ID. |
| memory_deleteA | Soft-delete a memory. Always confirm with the user before deleting. Deletions are reversible with memory_undelete, but limited to 5 per session as a safety measure. |
| memory_undeleteB | Restore a soft-deleted memory. |
| memory_historyA | Retrieve all versions of a logical memory. Pass any version ID in the chain. |
| memory_timelineA | Browse memories chronologically with cursor-based pagination. Returns titles and metadata only. |
| memory_relatedB | Find semantically related memories via embedding similarity. Returns titles only. |
| memory_migrateA | Discover and read memory files (CLAUDE.md, auto-memory) for migration into crowed. Returns file sections split by markdown headers. Review each section and decide whether it contains KNOWLEDGE (store with memory_store) or INSTRUCTIONS (skip).
This tool does NOT store anything. You review the sections and call memory_store for each piece of knowledge you want to keep. Skip pure instructions. |
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 10 tools
Each tool has a clearly distinct purpose: read by ID, search+read combined, store, update, delete, undelete, version history, chronological browsing, semantic relatedness, and migration from external files. No two tools perform overlapping functions.
All tools follow a consistent 'memory_verb' pattern in snake_case, with verbs like read, recall, store, update, delete, undelete, history, timeline, related, migrate. The naming is predictable and uniform.
10 tools is well-scoped for a memory management server, covering creation, retrieval, search, update, deletion (with undo), version history, chronological browsing, semantic relatedness, and migration. No tool is redundant.
The set covers full CRUD lifecycle (store, read/recall, update, delete/undelete), plus additional features like version history, timeline browsing, semantic relatedness, and migration from external formats. No obvious gaps for the stated domain of persistent memory management.