ClickHouse Loom
Self-hosted MCP server: shared agent memory, document search and a code index
- Pricing
- Open source
- Platforms
- self-hosted, API, Linux
- Runs
- Remotely
- Version
- 1.2.0
- Listing updated
- 2 days ago
About ClickHouse Loom
ClickHouse Loom is an open-source MCP server for databases. It runs as a hosted remote server, so there is nothing to install locally.
Loom is built by ClickHouse and keeps agent context and index data in ClickHouse, with Postgres selectable at first boot for live memory state. What one agent learns in a session can be found by the next, across Claude Code, Codex, Cursor or your own agents.
Beyond memory it offers a code index that answers questions about definitions, callers and change impact, document search with citations including PDF, docx and pptx, namespaces with roles and tokens for teams, and a record of runs, PR history and searchable conversations when recording is on. A dashboard ties memories, repositories and tasks together.
The README reports its own tests: with Loom, coding-agent runs cost about 20% less on one test and 21% on another, and memory retrieval cut reader tokens by 91% on LongMemEval-S. It says results are specific to the tested workloads. The stock install boots without API keys using a small local embedding model.
What it does
- Shared agent memory
- Memories saved by one agent are retrievable by others.
- Code index
- Definitions, callers and change impact for repositories.
- Cited document search
- RAG over files including PDF, docx and pptx.
- Multi-user mode
- Namespaces, roles and tokens for teams.
- Run history
- Records runs, outcomes and PR history.
- Docker and Helm
- Install with Docker or on Kubernetes.
Good for
- Let coding agents share context across sessions
- Give an agent application per-user memory via the SDK
- Query where a function is called before changing it
- Search internal documents with citations
Pricing
Open source
Open source, self-hosted
ClickHouse Loom FAQ
Where does the data live?
In ClickHouse by default; Postgres can be chosen at first boot for memory and knowledge state.
Does it need API keys to start?
No. The default install boots without keys, using a local embedding model and a placeholder LLM.
How do I install it?
Run the release install script, which starts Loom and ClickHouse and prints a dashboard URL at localhost:7777.
What is it not for?
The README says it is not an in-process library for short-lived memory, nor an agent framework.
Is ClickHouse Loom free?
Yes. ClickHouse Loom is open source, so you can use and self-host it for free.
What are the best alternatives to ClickHouse Loom?
The closest alternatives to ClickHouse Loom are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.
Alternatives to ClickHouse Loom

REA
MCP serverCLI and MCP server that lets coding agents reverse engineer apps and binaries
Runs locally- Open source
- 464K GitHub stars
- Developer tools

Codebase Memory
MCP serverLocal MCP server that builds a code knowledge graph for AI coding agents
Runs locally- Open source
- 48.7K GitHub stars
- Knowledge and memory

GitHub
MCP serverOfficial MCP server connecting AI assistants to GitHub repos, issues and workflows
Not checked yet- Remote
- Open source
- 34.5K GitHub stars
- Developer tools

Serena MCP: the IDE for your agent
MCP serverMCP toolkit giving coding agents symbol-level code retrieval and editing
Runs locally- Open source
- 31.5K GitHub stars
- Developer tools

XERJ
MCP serverLocal search engine for AI agents with cited answers over your code and docs
Runs locally- Open source
- 19.2K GitHub stars
- Knowledge and memory

Ouroboros
MCP serverSpec-first layer that pins requirements and verifies results of AI coding agent work
Runs locally- Open source
- 6.4K GitHub stars
- Developer tools