DevMemory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVMEMORY_PROJECTS | No | Comma-separated list of project name=path pairs, e.g., summet=C:/path,backend=C:/path2 |
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_projectsA | Returns registered Git projects for DevMemory(데브메모리). Reads devmemory.projects.json or DEVMEMORY_PROJECTS env. |
| search_all_projectsA | Searches multiple Git projects at once via DevMemory(데브메모리). Modes: timeline, daily, unfinished, overview. |
| get_commit_timelineA | Fetches commit timeline from a local repo or public GitHub URL via DevMemory(데브메모리). |
| explain_code_changesC | Explains which file, function, and lines changed and their purpose via DevMemory(데브메모리). |
| summarize_commitA | Analyzes commit diff and returns feature classification via DevMemory(데브메모리). |
| get_work_sessionA | Groups commits on a given date into work sessions via DevMemory(데브메모리). |
| find_unfinished_tasksA | Detects TODO, FIXME, and unimplemented markers via DevMemory(데브메모리). |
| generate_dev_reportB | Generates a daily/weekly dev report from commits and diffs via DevMemory(데브메모리). |
| resume_last_workA | Restores last work context and suggests next steps via DevMemory(데브메모리). |
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 9 tools
Tools like search_all_projects (timeline mode) and get_commit_timeline both retrieve commit timelines, and summarize_commit and explain_code_changes both analyze a commit's diff, which could cause confusion. However, each tool has a distinct primary purpose (searching vs fetching, summarizing vs explaining), and descriptions provide context.
All tools follow a consistent verb_noun pattern with snake_case: list_projects, search_all_projects, get_commit_timeline, etc. This makes it easy to predict behavior from the name.
9 tools is well within the typical range for a domain-specific server. Each tool addresses a distinct aspect of Git analysis and reporting, so none feel redundant.
The tool surface covers the full workflow: project discovery, searching, timeline retrieval, commit analysis, work session grouping, TODO detection, report generation, and context restoration. Minor omissions like a direct diff fetcher or project management actions are acceptable given the server's read-only analysis focus.