Skip to content

The repository is a Cursor plugin marketplace that installs Loom's MCP server and skills - #694

Merged
zlareb1 merged 9 commits into
mainfrom
feat/cursor-plugin
Nov 16, 2026
Merged

zlareb1 merged 9 commits into
mainfrom
feat/cursor-plugin

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

Changelog category (leave one):

  • New Feature

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-loom plugin installs Loom's MCP server and the loom and loom-code skills 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 and loom 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-skill Claude plugin does, so its skills are the root skills/ 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=true answers 401 with the resource_metadata pointer (server/transport/mcp_auth.py _bearer_challenge) that Cursor follows to a per-person browser sign-in. A team server without OAuth keeps loom 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

  • Wire: none.
  • Operator steps: to offer the plugin to a Cursor team, a team admin imports this repository under Dashboard → Plugins & MCPs → Add Marketplace → Import from Repo and sets 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.
  • Rollback: revert; nothing stored.

Tests

  • node validate-template.mjs from cursor/plugin-template (the template's own validator) against this tree: "Validation passed". Its two warnings are for no hooks/hooks.json and no root mcp.json; the manifest names .cursor-plugin/mcp.json instead.
  • 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 no Authorization header; the default URL equals the entry loom install --client cursor writes for a local server; the plugin ships exactly the root skills.
  • Not run: an install inside Cursor, which needs a signed-in Cursor account.

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 typecheck and make test-unit pass; the integration suite passes if server behaviour changed.
  • Generated files are regenerated in this PR, not by hand.
  • A new migration is additive and numbered after the latest on main; no merged migration is edited.
  • A behaviour change to any file a plugin ships bumps both plugin manifests' version, and no other open PR uses that version.
  • The frontend builds (npm --prefix frontend run build) and its tests pass, if frontend/ changed.
  • Docs under docs/ describe the system as it now is, and this description names any operator steps and wire changes.
  • Repository text has no dates, people, host names, internal namespaces, ticket or decision numbers; the history goes in this description (tests/unit/test_public_copy.py).
  • Commits are signed off (git commit -s), as CONTRIBUTING.md asks.

🤖 Generated with Claude Code

zlareb1 and others added 6 commits November 16, 2026 04:01
…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 and others added 3 commits November 16, 2026 04:11
…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>
@zlareb1
zlareb1 merged commit d88b943 into main Nov 16, 2026
55 checks passed
@zlareb1
zlareb1 deleted the feat/cursor-plugin branch November 16, 2026 04:42
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