Skip to main content
Glama

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-pi

Then in Pi:

/gzmo setup
/reload

Call gzmo_memory_status / gzmo_memory_search.


What you get

Piece

Role

This package

Pi extension (/gzmo …) + skill + wires gzmo-memory into MCP config

pi-mcp-adapter (bundled)

Lazy MCP tools so context stays small

GZMO binary

Product MCP server (gzmo mcp-serve) + local vault

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)

  1. Install GZMO binary + init vault:

curl -fsSL https://raw.githubusercontent.com/maximilianwruhs-cyber/GZMO/main/scripts/install-gzmo.sh | bash
  1. Install this Pi package:

pi install npm:gzmo-pi
  1. Wire MCP + verify:

/gzmo setup
/gzmo status

Restart 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

  1. Use the full repo: maximilianwruhs-cyber/GZMO

  2. 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)

  3. Deploy Redis + Neo4j + Qdrant next to your living gzmo.toml

  4. On the operator machine, prefer scripts/install-shared-mcp.sh (LAN gzmo-memory + Neo4j) instead of the laptop product fragment

  5. Keep this gzmo-pi package 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

/gzmo setup

Init ~/.gzmo if needed; merge gzmo-memory into Pi/shared MCP

/gzmo status

Binary, config, MCP wiring checklist

/gzmo living

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-pi

pi-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.


License

MIT

A
license - permissive license
Not graded
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

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

  • -
    license
    Not graded
    quality
    Not graded
    maintenance
    Integrates 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.
  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.
    1
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Offers MCP tools for managing a local AI memory vault, including remembering, searching, context packing, deletion, and verification of receipts.
    38
    Apache 2.0

View all related MCP servers

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.

View all MCP Connectors

Latest Blog Posts

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