Project Memory MCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initA | Initialize project memory system. Creates folder structure, generates project-specific prompts, and sets up claude.md instructions. Only run once per project. |
| parse-tasksA | Parse tasks from spec files or implementation plans. Extracts tasks with IDs, descriptions, acceptance criteria, dependencies, and adds them to tasks-active.json after user approval. |
| reviewB | Review uncommitted code changes. Analyzes git diff, checks against current tasks and architecture, identifies issues, and proposes task/architecture updates for user approval. |
| syncB | Sync project memory with recent commits. Updates tasks (marks completed), prunes commit log to last 20 commits, updates architecture if needed, and extracts new commands. |
| organizeA | Organize existing CLAUDE.md into project-memory structure. Migrates architecture, conventions, commands, tasks, and specs from CLAUDE.md to .project-memory/ files while keeping minimal references. Requires user approval. |
| create-specA | Create detailed specification from user requirements. Use this tool when: (1) user asks to create/write a spec, (2) user describes a feature they want to build, (3) user says "spec this" or "write a spec for". Clarifies ambiguity, validates against codebase, considers security/edge cases/tests, and writes spec to .project-memory/specs/. |
| refresh-promptsA | Refresh project-specific prompts with latest template improvements while preserving customizations. Backs up existing prompts, compares with new templates, identifies customizations, and merges them into updated templates. Requires user approval before modifications. |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: create-spec generates specifications, init sets up the system, organize migrates existing content, parse-tasks extracts tasks, refresh-prompts updates templates, review analyzes code changes, and sync integrates commits. The descriptions provide specific use cases and actions, making misselection unlikely.
All tool names follow a consistent verb-based pattern (e.g., create-spec, init, organize, parse-tasks, refresh-prompts, review, sync), using lowercase with hyphens for multi-word names. This uniformity makes the set predictable and easy to navigate, with no deviations in style.
With 7 tools, this server is well-scoped for managing project memory, covering initialization, organization, task parsing, prompt refreshing, code review, and synchronization. Each tool earns its place by addressing a specific aspect of the workflow without being excessive or insufficient.
The tool set provides complete coverage for the project memory domain, including setup (init, organize), content creation (create-spec, parse-tasks), maintenance (refresh-prompts, sync), and quality assurance (review). There are no obvious gaps, and the tools support a full lifecycle from initialization to ongoing updates.