ClickHouse Loom

Official ClickHouse Data & databases

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.

Remote server Needs a value: loom_host

Add to your client

Add the ClickHouse Loom MCP server to Claude Code

  1. Run the command

    claude mcp add --transport http clickhouse-loom https://<loom_host>/mcp
  2. Fill in the values ↓

  3. 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 · Secret

    A 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 Required

    Host 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.

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

This data comes from the Official MCP Registry.