Skip to content

Add ClickHouse Loom MCP server - #709

Open
zlareb1 wants to merge 3 commits into
Kilo-Org:mainfrom
zlareb1:mcp-clickhouse-loom
Open

zlareb1 wants to merge 3 commits into
Kilo-Org:mainfrom
zlareb1:mcp-clickhouse-loom

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 13, 2026 •

Copy link
Copy Markdown

Adds ClickHouse Loom's self-hosted MCP entry and generated catalog entry. Loom provides shared agent memory, document search and a repository code index. I work on Loom; Codex assisted with this update.

The prerequisites link the published quickstart and pin the installer to release 1.3.0. Install the server before adding the entry. The default local endpoint is loopback-only; team access requires your own reachable deployment and a scoped bearer token. The entry's transport, endpoint templates and token placeholders are unchanged.

Two installation options remain:

  • Local single-user server: http://localhost:7777/mcp?toolset=coding.
  • Team server: {{LOOM_URL}}/mcp?toolset=coding with the LOOM_API_KEY bearer parameter. Credentials are supplied by the user, never embedded in the catalog.

Validation for this update:

  • The repository's MCP catalog generator succeeds and produces the same other entries.
  • The released installer and an isolated 1.3.0 server passed readiness, authenticated MCP initialization, tools discovery, a permitted absent-key memory read and a missing-token 401 check. This used local embeddings and a development LLM, without paid inference.
  • These protocol checks do not establish a current Kilo UI or live team-endpoint test. Earlier client and full-suite evidence remains historical; broad tests and Kilo UI behavior were not rerun for this metadata update.

Only mcps/clickhouse-loom/MCP.yaml and its generated entry in mcps/marketplace.yaml change. No shared hosted service, default marketplace inclusion or performance result is claimed.

Comment thread mcps/clickhouse-loom/MCP.yaml Outdated
url: https://github.com/ClickHouse/loom
category: data
prerequisites:
- "A running Loom server. On one machine: curl -fsSL https://github.com/ClickHouse/loom/releases/latest/download/install.sh -o loom-install.sh && sh loom-install.sh (Docker)"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Pin the installer and declare Docker explicitly

This prerequisite tells users to download install.sh from releases/latest and run it with sh with no version pin and no checksum, so the exact code executed can change at any time and cannot be verified. It also depends on Docker, but Docker is only mentioned in parentheses rather than declared as a prerequisite, so installs on machines without Docker fail opaquely.

Minimal fix: reference a pinned release (or a published checksum) and add Docker as its own prerequisite entry, e.g. - Docker (the one-line installer runs Loom in a container).

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 729e7dc: Docker with the Compose v2 plugin (2.20 or later, which the installer checks) is now its own prerequisite, and the command points at the versioned installer releases/download/v1.2.0/install.sh. Loom publishes no checksum for install.sh itself; the installer verifies the stack bundle it downloads against the release's loom-stack.tar.gz.sha256, and the prerequisite says so.

Comment thread mcps/clickhouse-loom/MCP.yaml Outdated
}
}
parameters:
- name: Loom server URL

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Clarify that this must be the server origin without a trailing slash

The value is concatenated as {{LOOM_URL}}/mcp?toolset=coding, so an origin entered with a trailing slash (https://loom.example.com/) or with a path yields //mcp or a duplicated path and the connection fails. Naming the parameter for the expected form avoids that.

Suggested change
- name: Loom server URL
- name: Loom base URL (origin only, no trailing slash or path)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 729e7dc: the parameter is now "Loom base URL (origin only, no trailing slash or path)", as suggested. mcps/marketplace.yaml is regenerated; pnpm test and pnpm run typecheck:mcps pass.

@kilo-code-bot

kilo-code-bot Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)
  • mcps/clickhouse-loom/MCP.yaml
  • mcps/marketplace.yaml

Verification notes: Incremental review of 761d27e against 729e7dc (+6 / -2). The new prerequisite adds the quickstart link and states the loopback-only default and the team-deployment caveat; the installer reference moves from v1.2.0 to v1.3.0 with the bundle-checksum wording unchanged. Both earlier suggestions remain resolved (Docker/Compose is its own prerequisite, the installer is version-pinned, and LOOM_URL is named for the origin-only form). The generated mcps/marketplace.yaml entry still mirrors the source: the same three prerequisites in the same order, both content blocks, both parameters, and it stays alphabetically between browserbase and clickup. The new scalar is wrapped in the same style as the surrounding generated entries, and the Generate Marketplace workflow regenerates and commits any drift instead of failing, so a wrapping difference cannot break CI.

Not verifiable offline (unchanged from the prior review): that releases/download/v1.3.0/install.sh exists and verifies the stack bundle against the release-published SHA-256; that https://clickhouse.github.io/loom/getting-started/quickstart/ resolves; that Loom v1.3.0 serves MCP at /mcp?toolset=coding on port 7777; and that the default container binds to loopback only. Targeted maintainer checks: gh release view v1.3.0 --repo ClickHouse/loom --json assets, curl -fsI https://clickhouse.github.io/loom/getting-started/quickstart/, and from bin/, pnpm exec tsx generate-mcps-marketplace.ts followed by git diff --exit-code mcps/marketplace.yaml.

Previous Review Summaries (2 snapshots, latest commit 729e7dc)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 729e7dc)

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)
  • mcps/clickhouse-loom/MCP.yaml
  • mcps/marketplace.yaml

Verification notes: Incremental review of 729e7dc against 77e7e67. Both earlier suggestions are resolved: Docker with Compose v2 (2.20+) is now its own prerequisite, and the install command now points at the versioned releases/download/v1.2.0/install.sh with the checksum behavior documented. The LOOM_URL parameter is renamed to state the expected origin-only form, so the {{LOOM_URL}}/mcp?toolset=coding concatenation is no longer ambiguous. The regenerated mcps/marketplace.yaml entry matches the source definition exactly (prerequisites, content, parameters) and the header counts are unchanged.

Not verifiable offline: that releases/download/v1.2.0/install.sh exists and verifies its bundle against the release's published SHA-256, that Loom serves MCP at /mcp?toolset=coding on port 7777, and that the Docker installer binds to loopback only. Confirm those against a real Loom v1.2.0 server before merge.

Previous review (commit 77e7e67)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 2
Issue Details (click to expand)

SUGGESTION

File Line Issue
mcps/clickhouse-loom/MCP.yaml 9 Unpinned remote install script executed with sh and no checksum; Docker requirement only mentioned in parentheses instead of declared as a prerequisite
mcps/clickhouse-loom/MCP.yaml 27 LOOM_URL is concatenated with /mcp?toolset=coding; a trailing slash or path in the value produces a broken endpoint
Files Reviewed (2 files)
  • mcps/clickhouse-loom/MCP.yaml - 2 issues
  • mcps/marketplace.yaml - 0 issues (verified 129 MCPs, data: 53, alphabetical placement, and generated header counts)

Verification notes: id/directory agreement (mcps/clickhouse-loom ↔ clickhouse-loom), valid data category, per-content parameters scoping (consistent with mcps/context7 and mcps/neon), secret handling via {{LOOM_API_KEY}} placeholder only, and generated counts all check out; the generated catalog matches its source entry. Not verifiable offline: that releases/latest/download/install.sh exists, that Loom serves MCP at /mcp?toolset=coding on port 7777, that the Docker installer binds to loopback only, and that the streamable-http content matches the PR description's tested "type": "remote" entry. Confirm those against a real Loom server before merge.

Fix these issues in Kilo Cloud


Reviewed by deepseek-v4.1-flash-1017 · Input: 53.9K · Output: 20.5K · Cached: 990.6K

Review guidance: REVIEW.md from base branch main

@zlareb1

zlareb1 commented Nov 14, 2026

Copy link
Copy Markdown
Author

@alaapmurali a gentle ping on this one when you have a moment. Happy to change the wording, section or placement if you'd prefer. Thanks!

@zlareb1

zlareb1 commented Nov 18, 2026

Copy link
Copy Markdown
Author

Could a maintainer review this ClickHouse Loom MCP marketplace entry? Are any changes or additional information needed?

Use the released 1.3.0 installer and canonical setup guide while preserving the existing local and authenticated team connection configurations.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant