Projectmem
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECTMEM_ROOT | No | Absolute path to the project root (alternative to --root 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_instructionsA | Read the project's mandatory AI instructions. |
| get_summaryA | Read the project memory summary. |
| get_project_mapA | Read PROJECT_MAP.md to understand the repo structure. |
| get_planA | Read plan.md — the project's INTENT file (ideas + plans). |
| precheck_fileA | Check a file's failure history BEFORE modifying it. |
| get_issueA | Read one specific issue's full history by ID (token-efficient). |
| search_eventsA | Plain-text search across all logged events. |
| get_scoreA | Get the project's failure-prevention score. |
| get_contextA | Generate a token-budgeted memory context block. |
| get_global_gotchasA | Query cross-project library gotchas from ~/.projectmem/global/. |
| log_issueA | Open a new issue. Returns the issue ID. |
| record_attemptA | Record a fix attempt on the current issue. |
| record_fixA | Record a confirmed fix and close an issue. |
| add_decisionA | Record an architectural or product decision permanently. |
| add_noteA | Record a gotcha, setup detail, or other durable context. |
| list_projectsA | List the projects this server can reach, and which one is active. |
| current_projectA | Show which project a call would resolve to, without writing anything. Use this before a write when several projects are in play — it answers "where would this land?" cheaply. Read-only. |
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 17 tools
Each tool has a fairly distinct role, and the descriptions actively differentiate the read paths (get_summary vs. get_context vs. search_events vs. get_issue) and the write paths (log_issue vs. record_attempt vs. record_fix). The only real overlap is between list_projects and current_project, and between get_summary and get_context, but both pairs are explicitly contrasted in their text.
Most names follow a clean verb_noun snake_case pattern (get_summary, add_decision, record_fix, search_events). Minor deviations: current_project is noun-only with no verb, and the create-style verbs are mixed between 'log' (log_issue) and 'add' (add_decision, add_note), plus precheck_file reads as a bare verb prefix, but nothing is genuinely confusing.
17 tools is on the high side for a project-memory server, but nearly every tool maps to a distinct lifecycle step (read context, open issue, record attempt, record fix, persist decision/note, query history). The several read variants (summary, context, plan, map, instructions, score, gotchas) are justified by token-budgeting concerns rather than duplication.
The write lifecycle is well covered: issue -> attempt -> fix, plus decisions and notes, with reads for summary, plan, map, instructions, single issue, event search, context, and score. Gaps remain: there is no list_issues/enumerate-open-issues tool, no way to edit or supersede a note, and no delete/close-without-fix operation, though get_summary and search_events let agents work around most of these.