Ogham MCP — Shared Persistent Agent Memory

Practical Notes

• GitHub: 97 stars · 19 forks; pushed 2026-05-05 (verified via GitHub API).
• README quick start uses uvx --from ogham-mcp ogham init to write client configs and migrate schemas.
• README documents SSE mode with ogham serve --transport sse --port 8742 for multi-agent sharing.

Main

How to use memory without turning it into noise:

1. Decide what is “stable knowledge” (architecture decisions, conventions, runbooks) vs “ephemeral state”.
2. Only persist stable knowledge, and enforce a simple schema (component, decision, rationale, date).
3. When a task finishes, have the agent write a short memory entry, then validate retrieval by asking a new agent to solve a similar task.

If you have multiple agents running, prefer SSE mode so they share one server instance and database pool.

FAQ

Q: Do I need Supabase? A: No—README supports Supabase or Postgres (Neon/self-hosted).

Q: How do I connect different clients? A: Run the init wizard; it prints/writes client config snippets for common MCP clients.

Q: What transport should I use? A: stdio is simplest; use SSE when multiple agents should share one running server.