Pmll Memory Mcp
Attach persistent key-value context memory and Q-promise deduplication to your agent so repeated async work does not corrupt or duplicate state.
Overview
PMLL Memory MCP is a MCP server for the Build phase that offers persistent KV context memory and Q-promise deduplication for coding agents.
What is this MCP server?
- Persistent KV context memory for agent-accessible key-value state
- Q-promise deduplication to avoid duplicate in-flight async agent operations
- npm package pmll-memory-mcp over stdio (v0.1.1)
- Suits agents that fire parallel tool calls or retries
- Source in drQedwards/PPM repository on GitHub
- Server version 0.1.1
- npm identifier pmll-memory-mcp
- Repository: github.com/drQedwards/PPM
Community signal: 14 GitHub stars.
What problem does it solve?
Agents lose scratch state between turns and can duplicate async work when similar tool promises run in parallel.
Who is it for?
Builders experimenting with stateful agent loops who need simple durable keys and deduped promises in MCP.
Skip if: Production teams that require a managed vector DB, full audit UI, or mature SLAs from a hosted memory SaaS.
What do I get? / Deliverables
Your agent gains stable KV storage and deduplicated Q-promises so context and in-flight operations stay coherent.
- Persistent KV entries for agent context
- Deduped promise handling for repeated async ops
- More stable multi-step agent runs
Recommended MCP Servers
Journey fit
KV memory and deduplication are build-time agent infrastructure for reliable long-running coding sessions. Agent-tooling subphase is where MCP servers extend memory and coordination primitives beyond the default chat window.
How it compares
MCP KV memory with promise dedup, not a general-purpose embedding search or note-taking app.
Common Questions / FAQ
Who is PMLL Memory MCP for?
Developers wiring Claude Code or similar agents who need persistent KV memory and deduplicated async promises via MCP.
When should I use PMLL Memory MCP?
Use it while building agent workflows where parallel tool calls or session restarts make chat-only state insufficient.
How do I add PMLL Memory MCP to my agent?
Configure the pmll-memory-mcp stdio server from npm in your MCP settings and grant the agent access to its memory tools.