gzmo-pi
Provides graph/relationship memory for GZMO, enabling memory to be stored and queried as a graph.
Provides a hot session/cache plane for GZMO memory, supporting fast session state and caching.
Provides durable local vault storage with full-text search for curated memory.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gzmo-picheck my memory status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gzmo-pi
GZMO curated memory for Pi — Pi extension + MCP (via bundled pi-mcp-adapter).
Local-first by default (~/.gzmo SQLite vault). Optional living stack (Redis, Neo4j, Qdrant) documented below for operator hosts.
Gallery / install:
pi install npm:gzmo-piThen in Pi:
/gzmo setup
/reloadCall gzmo_memory_status / gzmo_memory_search.
What you get
Piece | Role |
This package | Pi extension ( |
pi-mcp-adapter (bundled) | Lazy MCP tools so context stays small |
GZMO binary | Product MCP server ( |
Product tools: gzmo_memory_status, gzmo_memory_search, gzmo_memory_turn_start, gzmo_memory_recall_pull, gzmo_memory_chain, gzmo_memory_profile, gzmo_wiki_search.
Related MCP server: engram
Quick start (laptop / product)
Install GZMO binary + init vault:
curl -fsSL https://raw.githubusercontent.com/maximilianwruhs-cyber/GZMO/main/scripts/install-gzmo.sh | bashInstall this Pi package:
pi install npm:gzmo-piWire MCP + verify:
/gzmo setup
/gzmo statusRestart Pi or /reload, then use gzmo_memory_status.
Manual MCP shape (if you prefer editing files):
{
"mcpServers": {
"gzmo-memory": {
"command": "/home/YOU/.local/bin/gzmo",
"args": ["mcp-serve"],
"env": {
"GZMO_CONFIG": "/home/YOU/.gzmo/gzmo.toml",
"GZMO_ALLOW_LAB_VAULT": "1",
"GZMO_PRODUCT": "1"
}
}
}
}Written to ~/.config/mcp/mcp.json and ~/.pi/agent/mcp.json by /gzmo setup.
Living stack (Redis · Neo4j · Qdrant)
The product path above is intentionally minimal: SQLite vault, embeddings off, no LAN services.
For the full curated-memory topology (operator / multi-host — honeypot at scale, graph, vectors):
Service | Typical role in GZMO |
SQLite | Durable vault + FTS (always) |
Redis | Hot session / cache plane |
Neo4j | Graph / relationship memory MCP |
Qdrant | Vector recall (when embeddings enabled) |
Suggested operator path
Use the full repo: maximilianwruhs-cyber/GZMO
Read:
docs/PRODUCT_MCP.md — product vs ops tools
Living / CT101 deploy docs in that repo (
docs/CT101_DEPLOY.md,docs/PI_GZMO_MEMORY_INTEGRATION.md)
Deploy Redis + Neo4j + Qdrant next to your living
gzmo.tomlOn the operator machine, prefer
scripts/install-shared-mcp.sh(LANgzmo-memory+ Neo4j) instead of the laptop product fragmentKeep this
gzmo-pipackage on workstations for the SQLite product vault; keep living MCP on the host that owns Redis/Neo4j/Qdrant
In Pi: /gzmo living prints the short pointer.
Commands
Command | Action |
| Init |
| Binary, config, MCP wiring checklist |
| Pointer to full Redis/Neo4j/Qdrant stack docs |
Develop
git clone https://github.com/maximilianwruhs-cyber/gzmo-pi.git
cd gzmo-pi
npm install
pi install .Publish (maintainers):
npm login # interactive; or: npm config set //registry.npmjs.org/:_authToken=…
npm pack --dry-run # expect ~tens of KB, not tens of MB
npm publish --access public
# then: https://pi.dev/packages/gzmo-pipi-mcp-adapter is a normal dependency (installed by pi install / npm install), not bundledDependencies — bundling it pulled ~57MB of transitive SDK tree into the tarball.
Links
Product binary / vault: GZMO
Pi packages: pi.dev/packages
MCP adapter: pi-mcp-adapter
License
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceIntegrates the Mem0 Memory API with MCP-compatible clients to provide AI agents with persistent, long-term memory capabilities. It enables users to add, search, update, and delete memories to maintain context and personalization across different interactions.
- AlicenseNot gradedqualityCmaintenanceProvides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.1MIT

Enigma MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceOffers MCP tools for managing a local AI memory vault, including remembering, searching, context packing, deletion, and verification of receipts.38Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to have a living memory with atomic knowledge storage, multi-factor recall, organic decay, automatic learning, and graph traversal via MCP.1MIT
Related MCP Connectors
Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.
Cross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client.
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/maximilianwruhs-cyber/GZMO-Pi-'
If you have feedback or need assistance with the MCP directory API, please join our Discord server