ClickHouse Loom
Lets an agent store shared memories, search documents, and explore code with ClickHouse Loom. Summary written by AI Index.
The registry’s description: Shared long-term memory, document search and a code index for AI agents, self-hosted on ClickHouse.
loom_host Add to your client
Add the ClickHouse Loom MCP server to Claude Code
Run the command
claude mcp add --transport http clickhouse-loom https://<loom_host>/mcpFill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to Cursor
Open mcp.json· Where the file is:
~/.cursor/mcp.json,.cursor/mcp.jsonPaste the server entry
{ "mcpServers": { "clickhouse-loom": { "url": "https://<loom_host>/mcp" } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to VS Code
Open mcp.json· Where the file is:
.vscode/mcp.jsonPaste the server entry
{ "servers": { "clickhouse-loom": { "type": "http", "url": "https://<loom_host>/mcp" } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to Codex
Run the command
codex mcp add clickhouse-loom --url https://<loom_host>/mcpFill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to Claude
Open Claude’s MCP config
- Open Customize > Connectors.
- Choose Add custom connector.
- Enter the server URL below.
- Add OAuth credentials under Advanced settings if the server needs them, then choose Add.
Server URL
https://<loom_host>/mcpFill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to ChatGPT
Open ChatGPT’s MCP config
- Go to chatgpt.com/plugins.
- Choose the plus button, then Add custom MCP server.
- Enter a name and description.
- Under Connection, enter the server URL below.
- Set up authentication, then choose Create as a plugin.
Server URL
https://<loom_host>/mcpFill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to Devin Desktop
Open mcp_config.json· Where the file is:
~/.config/devin/mcp_config.json,%APPDATA%\devin\mcp_config.jsonPaste the server entry
{ "mcpServers": { "clickhouse-loom": { "serverUrl": "https://<loom_host>/mcp" } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to Gemini CLI
Open settings.json· Where the file is:
~/.gemini/settings.json,.gemini/settings.jsonPaste the server entry
{ "mcpServers": { "clickhouse-loom": { "httpUrl": "https://<loom_host>/mcp" } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to GitHub Copilot
Run the command
copilot mcp add --transport http clickhouse-loom https://<loom_host>/mcpFill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to Cline
Open cline_mcp_settings.json· Where the file is:
~/.cline/data/settings/cline_mcp_settings.jsonPaste the server entry
{ "mcpServers": { "clickhouse-loom": { "type": "streamableHttp", "url": "https://<loom_host>/mcp" } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to Kiro
Open mcp.json· Where the file is:
.kiro/settings/mcp.json,~/.kiro/settings/mcp.jsonPaste the server entry
{ "mcpServers": { "clickhouse-loom": { "url": "https://<loom_host>/mcp" } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to Zed
Open settings.json
Paste the server entry
{ "context_servers": { "clickhouse-loom": { "url": "https://<loom_host>/mcp" } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to OpenCode
Open opencode.json· Where the file is:
~/.config/opencode/opencode.json,opencode.jsonPaste the server entry
{ "$schema": "https://opencode.ai/config.json", "mcp": { "clickhouse-loom": { "type": "remote", "url": "https://<loom_host>/mcp", "enabled": true } } }Fill in the values ↓
Check it’s connected
Add the ClickHouse Loom MCP server to JetBrains AI Assistant
Open JetBrains AI Assistant’s MCP config
- Open Settings | Tools | AI Assistant | Model Context Protocol (MCP).
- Choose Add.
Paste the server entry
{ "mcpServers": { "clickhouse-loom": { "url": "https://<loom_host>/mcp" } } }Fill in the values ↓
Check it’s connected
If the file already has servers, add the entry inside the existing object. To check it’s connected, restart or reload the client and look for clickhouse-loom in its list of MCP servers. A server that needs sign-in opens it on first use.
What you fill in
Required values appear as <NAME> placeholders in the snippets; add optional ones the same way. Descriptions are the server’s registry entry’s.
<Authorization>HTTP header Optional · SecretA writer token from the dashboard (Settings, Tokens) or `loom mint-token`; leave the header out when the server signs in through the browser
<loom_host>Value RequiredHost name of your Loom server, with :port when it is not 443
Client compatibility
By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.
- Claude Code Transport supported
- Cursor Transport supported
- VS Code Client docs don’t list transports
- Codex Transport supported
- Claude Client docs don’t list transports
- ChatGPT Transport supported
- Devin Desktop Transport supported
- Gemini CLI Transport supported
- GitHub Copilot Client docs don’t list transports
- Cline Transport supported
- Kiro Transport supported
- Zed Client docs don’t list transports
- OpenCode Client docs don’t list transports
- JetBrains AI Assistant Transport supported
Agent Skills: ClickHouse
clickhouse-architecture-advisor, clickhouse-best-practices, chdb-datastore, chdb-sql, clickstack-otel-collector, ClickHouse, infra-clickhouse, infra-postgres, clickhouse-js-node-troubleshooting, clickhouse
Sources
- Official MCP Registry registry.modelcontextprotocol.io · checked Nov 14, 2026
- GitHub organization clickhouse (verified domain) github.com · checked Nov 14, 2026
This data comes from the Official MCP Registry.