Repository navigation
The repository is a Cursor plugin marketplace that installs Loom's MCP server and skills - #694
Merged
Merged
Conversation
…P server and skills .cursor-plugin/ at the root holds the marketplace, the clickhouse-loom manifest and its MCP entry. The entry is the server's MCP URL alone, a plugin variable: a single-user server serves it without a token, and a server with OAuth on signs each person in by browser. The plugin ships the root skills, and the release pins its version with theirs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…Auth URL Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…ow stands alone Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…skills are listed as a piece Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…, and its listing reads as not submitted Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…h rule covers Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
zlareb1
force-pushed
the
feat/cursor-plugin
branch
from
November 16, 2026 04:04
a9661fd to
5184201
Compare
…every Cursor link says untested Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…page says the admin imports it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…nstall writes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog category (leave one):
Changelog entry (one or two sentences a user of Loom can read without the diff; the release pull request collects these into the release notes):
The repository is a Cursor plugin marketplace: the
clickhouse-loomplugin installs Loom's MCP server and theloomandloom-codeskills in Cursor, with one variable, the server's MCP URL. A team admin on a Cursor Teams or Enterprise plan imports it as a team marketplace and sets that URL; it is not listed in Cursor's marketplace and is untested in Cursor. A single-user server on the same machine needs no sign-in, and a server with OAuth on signs in by browser.Why
Cursor lists plugins in its marketplace only from a repository that carries a
.cursor-plugin/manifest (cursor.com/docs/reference/plugins). Until now Cursor users had only the install link andloom install --client cursor, and no one-step install of the MCP entry and the skills together. With this change, the repository can be submitted at cursor.com/marketplace/publish.The plugin lives at the repository root, as the
loom-code-skillClaude plugin does, so its skills are the rootskills/with no second copy to drift. The release pins its version with the root skills'.The MCP entry is the URL alone. A Cursor plugin variable is set by a team admin for the whole team, so a bearer token there would be one shared token for everyone. Without a header, a single-user server serves the call, and a server with
LOOM_OAUTH_ENABLED=trueanswers 401 with theresource_metadatapointer (server/transport/mcp_auth.py_bearer_challenge) that Cursor follows to a per-person browser sign-in. A team server without OAuth keepsloom install --client cursor, which the Cursor page says.Scope and risk
New files:
.cursor-plugin/{marketplace.json,plugin.json,mcp.json}, plus the docs pages that offer the plugin. The plugin has no hooks, so nothing runs in a user's session beyond the MCP connection. Server code is unchanged. The release script gains one version pin. Listing the plugin publicly needs a one-time submission at cursor.com/marketplace/publish (repository URL; the marketplace file is at the root).Compatibility, rollout and rollback
LOOM_MCP_URL. A public listing needs a one-time submission at cursor.com/marketplace/publish, which Cursor reviews by hand. A server deployment needs no change.Tests
node validate-template.mjsfromcursor/plugin-template(the template's own validator) against this tree: "Validation passed". Its two warnings are for nohooks/hooks.jsonand no rootmcp.json; the manifest names.cursor-plugin/mcp.jsoninstead.tests/unit/test_cursor_plugin.py: the marketplace entry names the root plugin; manifest paths are relative and exist; every${VAR}in the MCP entry is a declared, required variable; the entry sends noAuthorizationheader; the default URL equals the entryloom install --client cursorwrites for a local server; the plugin ships exactly the root skills.AI assistance in the code (leave one; writing this description with AI is fine):
AI-generated (an agent wrote most of the diff): Claude Code. The plugin schema was checked against Cursor's plugin reference and template validator.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist
make format-check,make lint,make typecheckandmake test-unitpass; the integration suite passes if server behaviour changed.main; no merged migration is edited.npm --prefix frontend run build) and its tests pass, iffrontend/changed.docs/describe the system as it now is, and this description names any operator steps and wire changes.tests/unit/test_public_copy.py).git commit -s), as CONTRIBUTING.md asks.🤖 Generated with Claude Code