Repository navigation
Conversation
|
Upstream freshness check: the official Global plugin on |
|
One catalog gap and one freshness fix: this PR currently packages only the Global plugin from main (the README China link points to a separate branch, so the China plugin is not installable through this catalog entry). The official cn branch has its own Cursor manifest and uses https://klingai.com/mcp/plugin; main uses https://kling.ai/mcp/plugin. Both upstream manifests are now version 1.4.2, while this PR snapshot is 1.4.1. Could the catalog include a separate China entry or install path and refresh the snapshot to 1.4.2? |
|
Update: the current PR head now contains both upstream Cursor plugin snapshots at v1.4.2: |
14294a0 to
dd8f22b
Compare
|
I updated the branch on current main to resolve the Marketplace index and README conflicts, preserving the upstream Sabre entry and both Kling regional entries. I rechecked the manifest JSON and confirmed the Global and China endpoints still point to their official |
Summary
Add the official Kling AI Cursor plugin for both account regions as separate installable catalog entries:
kling-ai— Global, usinghttps://kling.ai/mcp/pluginkling-ai-cn— China, usinghttps://klingai.com/mcp/pluginBoth snapshots are current at version
1.4.2. The Global files are synced from upstreamklingai-tech/cursor-plugincommitb8fd57002fac0f4fb4a157cc5a8042fb0d203aa5; the China files are synced from itscnbranch commita6e554bd3e09ee6421cc67793130e89e26e7f091. The catalog gives the China snapshot a distinct ID so the two regional plugins can be installed separately. OAuth and generated work use the account region's Kling service and credits.Disclosure: I work at Kling AI and help with these integrations. This is a free catalog contribution; no paid placement or generation test is involved.