Developer · Local MCP server
Project Memory MCP
Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.kaaustubh/project-memory-mcp- Version
- 1.6.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-03
- Updated
- 2026-07-03
- Publisher
- kaaustubh (GitHub)
- Repository
- github.com/kaaustubh/project-memory-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @kaaustubh/project-memory-mcp | 1.6.0 | stdio |
How to connect Project Memory MCP
Project Memory MCP runs locally from a Node.js package published to the npm registry: @kaaustubh/project-memory-mcp version 1.6.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @kaaustubh/project-memory-mcp@1.6.0. It reads the environment variable PROJECT_MEMORY_ROOT; set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"project-memory-mcp": {
"command": "npx",
"args": [
"-y",
"@kaaustubh/project-memory-mcp@1.6.0"
],
"env": {
"PROJECT_MEMORY_ROOT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ProfitPlayMCP server for the live ProfitPlay BTC five-minute AI agent sandbox. | Local · stdio |
| ProfusiaGive your AI a place to publish: living pages with live data, shareable links, no deploy pipeline. | Remote · HTTP |
| Project BrainRead-only source search and retrieval across configured GitHub repositories. | Local · stdio |
| Project ContextSafely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud. | Local · stdio |
| ProjectmemCoding agent memory — one local MCP server for every project. Warns before repeating failed fixes. | Local · stdio |
| projectmindPersistent project memory for AI coding agents: one compact digest instead of re-reading the repo. | Local · stdio |
| ProjectPulse MCPMonitor GitHub repo health, DORA metrics and CI signals from your AI assistant. | Local · stdio |
| ProjGraph MCP ServerAnalyze.NET solutions: Generate Mermaid graphs, ERDs, class diagrams, and project metrics. | Local · stdio |