Repository navigation
packages
Droid Wiki Bot edited this page Aug 24, 2026
·
2 revisions
Memongo's packages/ directory holds seven workspace packages. apps/api depends on the bridge and engine; apps/mcp, packages/tools, and external consumers depend on packages/client. See Architecture for how these fit together.
| Package | Purpose |
|---|---|
@memongo/memory-engine |
Core MongoDB memory engine: embeddings, graph, episodes, search, knowledge base, and analytics. |
@memongo/memory-bridge |
Stable facade between apps/api and the engine, so the engine's internal types can change without breaking the API. |
@memongo/memory |
Published re-export barrel (package dir packages/memongo-memory) that combines the bridge and engine into one npm import. |
@memongo/client |
TypeScript HTTP client SDK (MemongoClient) for the apps/api /v1/* routes. |
@memongo/tools |
AI SDK tool helpers (Vercel AI SDK, OpenAI) built on top of packages/client. |
@memongo/lib |
Shared types, contract definitions, auth, and utilities used across the workspace (private, internal). |
@memongo/pi-extension |
Pi coding-agent extension that adds semantic memory to Pi sessions. |
- Architecture — how the API, bridge, engine, and MongoDB fit together
- Apps — the HTTP API, MCP server, and web console that consume these packages
- Reference: data models — full type catalogs referenced by the bridge and client