Practical overview
When it fits
Use it when coding-agent context needs to persist across sessions or be shared across clients, and you can provide a database and embedding provider.
Who it is for
- Developers who want coding-agent context to persist between sessions.
- Teams or workflows that use multiple MCP-compatible coding-agent clients and want them to share a database-backed memory.
Documented uses
- Preserve project decisions, codebase context and recurring gotchas between coding sessions.
- Retrieve saved agent context from a different connected client.
- Search for relationships between remembered facts using structured retrieval.
Requirements & limits
The repository identifies the project as open source under the MIT license.
- A database is required; documented choices include Supabase and Neon, plus self-hosted Postgres.
- An embedding provider must be selected; examples include OpenAI, Ollama, Mistral and Voyage.
- The default stdio mode starts a server process per MCP client; Streamable HTTP is documented for multiple agents sharing one instance.
- The repository describes hybrid search and a typed-edge graph alongside vector search.
- The project documents Docker distribution and Python 3.13+ support.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up Ogham MCP with the initialization wizard
Connect a database and embedding provider, then prepare Ogham's MCP client configuration.
Before you start
- A Supabase project or Neon database; self-hosted Postgres is also supported with the Postgres extra.
- An embedding provider and its credentials.
- For Neon or self-hosted Postgres, install the postgres extra.
Steps
Run
uvx --from ogham-mcp ogham init; for Neon or self-hosted Postgres, useuvx --from 'ogham-mcp[postgres]' ogham init.Follow the wizard to connect the database, choose an embedding provider and apply the schema migration.
Use the generated client configuration; for Claude Code the wizard runs
claude mcp add, while for other clients it prints a configuration snippet.
Expected outcome
The database is prepared and the MCP client configuration is written or provided. The README describes then asking an agent to save a memory and retrieve it later, including from another client sharing the database.
Guide limitations
- This guide covers wizard setup; actual agent use depends on configuring and connecting a compatible MCP client.
- The database and embedding provider are prerequisites, not included as Ogham services.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- ogham-mcp/ogham-mcp · Official homepage title · retained in its source language

