@dev-vortex/pi-muninn-mcp
v0.1.0
Published
MCP server exposing @dev-vortex/pi-muninn memory/continuity tools to Claude Code.
Readme
@dev-vortex/pi-muninn-mcp
MCP server that gives Claude Code direct access to @dev-vortex/pi-muninn's project-memory and continuity tools — check status, write, and query project memory without going through a Pi session or an LLM round-trip.
Requirements
@dev-vortex/pi-muninninstalled and enabled for Pi (pi install @dev-vortex/pi-muninn)- Node.js >= 22
Install
Register it with Claude Code, either globally (applies to every project):
claude mcp add --scope user pi-muninn-mcp -- npx -y @dev-vortex/pi-muninn-mcpor per-project, in that project's .mcp.json:
{
"mcpServers": {
"pi-muninn-mcp": { "command": "npx", "args": ["-y", "@dev-vortex/pi-muninn-mcp"] }
}
}Claude Code prompts to approve the server on first use either way.
Tools
| MCP tool | Purpose |
|------------------------------|-------------------------------------------------------------|
| pi_project_memory_status | Report whether project memory is enabled and its db state |
| pi_project_memory_enable | Enable/disable project-scoped memory for a workspace |
| pi_continuity_write | Persist a plan/decision/discovery/progress/outcome entry |
| pi_continuity_query | Query stored continuity entries |
| pi_memory_search | Semantic search across stored memories |
| pi_memory_save | Explicitly save a fact/decision to persistent memory |
Every tool takes an optional projectRoot; when omitted it targets whatever project Claude Code currently has open.
Getting Claude to use these tools well
Tool descriptions alone cover per-call parameters, not judgment calls like "check status before starting work" or "write continuity as you go." This package ships a CLAUDE.md usage policy — copy it into your own project (or your global ~/.claude/CLAUDE.md) to cover exactly that.
License
MIT
