ClickHouse Loom
What it does
Shared long-term memory, document search and a code index for AI agents, self-hosted on ClickHouse.
- Connects Runs in the cloud
- Account or key Needs Authorization
- Category Databases & datasets
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · What you ask goes through the maker’s server ({loom_host}) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a ClickHouse Loom key (create it on the maker’s site) · The address has {…} parts you must replace with your own first · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
Sign up and create a ClickHouse Loom key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Open Claude’s Connectors page
CustomizeConnectors
Click “Add” → “Custom” → “Web” and fill in these 2 fields
Copy each value into the field with the same name in Claude, then click Continue
Name · NameClickHouse LoomRemote MCP server URL · Addresshttps://{loom_host}/mcpUnder Request headers, add this name and value
Header nameAuthorizationValueBearer <paste your key here>Paste the key only into the app’s field, never into a chat or to anyone
Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
Turn it on in a chat
+ConnectorsClickHouse Loom
Try it
Use ClickHouse Loom and tell me what you can do for me, then show me one thing✓ If Claude says it is using ClickHouse Loom or shows a ClickHouse Loom tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect ClickHouse Loom yet
ClickHouse Loom needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify
What you can do instead
A · Use an app that can connect ClickHouse Loom
- You need a ClickHouse Loom key (create it on the maker’s site) · The address has {…} parts you must replace with your own first · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
- You need a ClickHouse Loom key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
- You need a ClickHouse Loom key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
- You need a ClickHouse Loom key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
B · Others in Databases & datasets that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Supabase✓ ChatGPT
- Appwrite MCP✓ ChatGPT
- Pg Aiguide✓ ChatGPT
Works with Claude Code, with some setup first
You need a ClickHouse Loom key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
Sign up and create a ClickHouse Loom key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --transport http --scope user loom 'https://{loom_host}/mcp' --header 'Authorization: Bearer {token}'Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
Type /mcp in Claude Code
You should see ClickHouse Loom listed as connected
Try it
Use ClickHouse Loom and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using ClickHouse Loom or shows a ClickHouse Loom tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a ClickHouse Loom key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
Sign up and create a ClickHouse Loom key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Open Cursor’s MCP settings file
~/.cursor/mcp.json
Paste these settings, fill in the empty values and save
{ "mcpServers": { "loom": { "url": "https://{loom_host}/mcp", "headers": { "Authorization": "Bearer {token}" } } } }Fill in your key
In the ClickHouse Loom settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Open the AI chat in Cursor in Agent mode
Try it
Use ClickHouse Loom and tell me what you can do for me, then show me one thing✓ If Cursor says it is using ClickHouse Loom or shows a ClickHouse Loom tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a ClickHouse Loom key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
Sign up and create a ClickHouse Loom key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Open VS Code’s MCP settings file
MCP: Open User Configuration
Paste these settings, fill in the empty values and save
{ "servers": { "loom": { "type": "http", "url": "https://{loom_host}/mcp", "headers": { "Authorization": "Bearer {token}" } } } }Fill in your key
In the ClickHouse Loom settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Open the AI chat in VS Code in Agent mode
Try it
Use ClickHouse Loom and tell me what you can do for me, then show me one thing✓ If VS Code says it is using ClickHouse Loom or shows a ClickHouse Loom tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://{loom_host}/mcpJSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Over the web
Claude Code
claude mcp add --transport http --scope user loom 'https://{loom_host}/mcp' --header 'Authorization: Bearer {token}'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"loom": {
"url": "https://{loom_host}/mcp",
"headers": {
"Authorization": "Bearer {token}"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"loom": {
"type": "http",
"url": "https://{loom_host}/mcp",
"headers": {
"Authorization": "Bearer {token}"
}
}
}
}Values you fill in
- A writer token from the dashboard (Settings, Tokens) or `loom mint-token`; leave the header out when the server signs in through the browser
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- Not on npm/PyPI
- Connection
- Runs in the cloud
- Transport
- streamable-http
- Latest versioni
- 1.2.0
- Categoryi
- Databases & datasets
- Published to registryi
- Nov 13, 2026
- Code last changedi
- Nov 13, 2026
- Maker
- ClickHouse
- Website
- github.com
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Related guides
What it can do
The address needs your own values, so we cannot read the tool list for you.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ClickHouse, which owns the repo
- ✓ Pass
Still maintained
Code last changed today
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
- – Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Databases & datasetsi
- More stars than 92% of the other 1184 servers in this category
- Published to the registry more recently than 96% of the other 1184 servers in this category
- Basic checks equal to or better than 100% of the other 1184 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is ClickHouse Loom safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: Authorization
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed today, and the latest version (1.2.0) reached the registry today.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
What can I use instead?
In the same category: Dbx, MCP Toolbox for Databases, MCP Toolbox for Databases
Others in the same category
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
ClickHouse Loom
Shared memory, document search and code intelligence for AI agents.
For Claude Code, Codex, Cursor and your own agents.
English · 简体中文 · 日本語 · 한국어 · Português (Brasil) · Español · Русский
What Loom is for · Benchmarks · Get started · Capabilities · Integrations · Documentation
Loom is an open-source, self-hosted MCP server that gives your agents long-term, shared memory: what one agent learns in a session, the next agent or tool can find.
Agents connect through MCP, HTTP, Python or TypeScript. Self-host with Docker or on Kubernetes with the Helm chart; agent context and index data live in ClickHouse, and a deployment can choose Postgres at first boot for live memory and knowledge state. The dashboard brings memories, repositories, tasks and runs into one place.
What Loom is for
- Long-term memory shared across your coding agents, with plugins that load context at session start and capture the session as it runs. Agent memory · Connect a coding agent
- Memory for an agent application, per user, from the Python or TypeScript SDK. Your first agent
- A multi-user MCP memory server with namespaces, roles and tokens. Multi-user mode · Namespaces and sharing
- A code index of your repositories that coding agents query for definitions, callers and change impact. Code index
- Lower model cost for coding agents, as measured below. Coding-agent cost
- Document search with citations (RAG), including PDF,
.docxand.pptxfiles the extractor service converts. Document search - Shared context for multi-agent workflows: shared memory, task inboxes and decisions. Multi-agent
- Memory, recall, audit and erasure for autonomous agents. Autonomous agents
- A record of agent work, with searchable conversations (when recording is on), session briefs to resume from, runs with their goals, outcomes and model costs when supplied, and PR and tracker history. Runs and PR history
Every use case, and when another tool fits better: use cases.
Loom is not an in-process library for one agent's short-lived memory, nor an agent framework. When Loom does not fit
Measured results
| Evaluation | With Loom | Without Loom | Efficiency gain | Scope |
|---|---|---|---|---|
| Coding-agent answer quality | 0.84 | 0.78 | 20% lower model cost | 24 questions × 3 paired runs |
| Coding-agent file localization | 96.4% | 91.4% | 21% lower model cost | 36 questions × 10 paired runs |
| Memory vs full-history answers | 94% | 90% | 91% fewer reader prompt tokens | 100 paired LongMemEval-S questions |
Both coding setups use Claude Code (claude-sonnet-5) on the ClickHouse codebase; cost is the whole session's model bill, excluding Loom's server-side model calls, hosting and indexing. Answer quality measures coverage of a verified answer's key points, with a contradiction penalty. File localization counts whether the right file is among the up to three files the agent is asked to name at the end of its answer.
The memory row compares retrieved memories with full conversation history using the same gpt-5 reader. Token savings exclude memory construction; the 94% vs 90% accuracy difference is descriptive, not statistically established.
Separately, Loom's `memory.ask` configuration scored 96.6% answer accuracy on all 500 LongMemEval-S questions. This is a product evaluation with its own configured answer models, not the fixed-reader comparison above.
Results are specific to the tested workloads.
Protocols and reproducible artifacts · detailed results · evaluate on your workload
Get started
1. Choose your Docker setup
- Personal use—the default: no login, localhost-only access and a
dev/localnamespace. One person can connect multiple agents. - Team use: authenticated accounts and namespace access controls. Start in multi-user mode from the first boot.
Both modes support the same Loom features, including configured LLMs and embeddings. Single-user is not a reduced-feature edition. You can also switch an existing installation without deleting its data; grant new accounts access to the existing namespaces.
To try it with nothing installed, open it in a codespace:
(what it runs and who can reach it)
For the default personal installation, with Docker installed (on Windows, in a WSL 2 terminal where docker works: Docker Desktop with its WSL integration on, or Docker Engine installed in the distribution):
curl -fsSL https://github.com/ClickHouse/loom/releases/latest/download/install.sh -o loom-install.sh && sh loom-install.sh && rm loom-install.sh
Run it from your home directory, or another directory only you can write to. The installer starts Loom and ClickHouse, applies migrations and prints the dashboard URL: http://localhost:7777/; on a new install it then checks that a memory saves and reads back. On a terminal it also offers to connect the coding agents it finds (Claude Code, Codex, VS Code) and, on a new install, opens the dashboard. The image includes the server, workers, dashboard and Python, TypeScript and Go compiler indexers, plus the C++ one on amd64; TypeScript dependencies are prepared automatically. Quickstart and pinned releases
The installation lives in ~/.loom (LOOM_INSTALL_DIR chooses another directory): the Compose file and the startup settings in ~/.loom/.env. Running the install command again upgrades in place and keeps your .env settings.
Keep single-user mode localhost-only. For shared access, follow the team deployment guide, including TLS.
2. Configure models and API keys
The stock installation boots without keys or network. Storage, the dashboard, structural code indexing and semantic search work, on a small local embedding model the image carries; the fake LLM gives no AI-generated answers.
| Component | Configure for real use | Without configuration |
|---|---|---|
| Embeddings | Provider, embedding model, dimensions and API key. | local (bge-small on CPU): semantic retrieval, weaker than a hosted model. |
| LLM | Provider, model and API key. | fake-echo-1: no meaningful extraction, summaries or answers. |
Open Settings → Models & keys, choose both providers and models, enter their keys, then click Test & apply. No Docker restart is needed; changing the embedding space rebuilds the existing index. The dashboard's embedding choices are hosted providers: to keep local and add an LLM, set the LLM lines in ~/.loom/.env instead (Models and keys).
One OpenAI API key can serve both roles. Claude needs a separate embedding provider. OpenAI, Gemini and OpenAI-compatible embedding endpoints are supported. Your agent's CLI login or subscription does not supply Loom's provider keys.
Prefer environment configuration? Edit ~/.loom/.env, then recreate the server:
docker compose --project-directory "$HOME/.loom" up -d --force-recreate loom
A key alone does not change the pinned models (the local embedder and the fake LLM); set the provider and model too. Saved dashboard settings take precedence over .env. Follow models and API keys for provider recipes and health checks.
Everything else is in one file. loom.example.yaml lists every setting with its default and what it does, by area: the ClickHouse connection, timeouts and budgets, rate limits, workers, and the *_enabled switches that turn features on and off. Set any of them as LOOM_ in ~/.loom/.env and recreate the server; a deployment that mounts a config file can set them in a copy of this file instead (how settings are read). One marked live also changes while Loom runs: loom settings set , or Admin → Deployment settings. loom settings list --changed shows what differs from the defaults and where each value came from (runtime settings).
3. Connect your agents
If the installer connected your agent, skip the commands below. On the machine running a personal installation, the plugins need no token:
# Claude Code
claude plugin marketplace add ClickHouse/loom claude plugin install loom@loom
Codex
codex plugin marketplace add ClickHouse/loom codex plugin add loom@loom
Start a new session; the first one connects to http://localhost:7777. In Codex, run codex interactively once and approve the plugin's hooks; until then only the tools work. Tell the agent something worth keeping, then ask about it in the next session.
For Cursor on the machine running a personal installation, the button below adds the local MCP entry, which needs no token:
[![Add Loom to Cursor