Dev Context 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_memory_sectionsA | List all available memory sections. Use this to discover what project context is stored. Returns section names and descriptions. |
| read_memoryA | Read a memory section. Use this to retrieve stored project context such as architecture decisions, API contracts, conventions, bugs, todos, or glossary. Prefer reading memory before scanning unrelated source files. |
| write_memoryA | Overwrite a memory section with new content. WARNING: This replaces the entire section. Use with care. Prefer append_decision or append_api_contract for adding entries. Only use write_memory when you need to restructure or rewrite a full section. |
| append_decisionA | Record an architecture or design decision. Use this after making a significant technical choice. Stores a structured ADR (Architecture Decision Record) with context, decision, consequences, and related files. Do not store full source code — store only the rationale and outcome. |
| append_api_contractA | Use this tool after creating or modifying an API endpoint. Store only the durable endpoint contract: method, path, auth, request shape, response shape, side effects, frontend usage, and related files. Do not store full source code. |
| search_memoryA | Use this tool before scanning the codebase when the user asks about project architecture, API contracts, decisions, bugs, conventions, or previous implementation choices. Searches all memory sections using keyword matching and returns matching lines with surrounding context. |
| summarize_memoryA | Get a compact overview of project memory. Returns headings and short excerpts for each section. Use this for a quick orientation before diving into specific sections with read_memory. |
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 clear, distinct purpose: append tools for adding structured entries, retrieval tools for accessing memory, and write for overwriting sections. No ambiguity between tools.
All tools follow a consistent verb_noun pattern in snake_case (e.g., append_api_contract, list_memory_sections), making the set predictable and easy to navigate.
With 7 tools covering creation, retrieval, and overwriting of memory sections, the set is well-scoped. Each tool earns its place without being redundant or excessive.
The tools support appending and reading memory, but lack explicit delete or edit functionality for sections or individual entries. write_memory can overwrite but not delete, and no tool allows partial updates.