feat: add Kimi Code and Grok Build plugin support#42
Closed
Rodriguespn wants to merge 5 commits into
Closed
Conversation
Extend the multi-vendor plugin layout so the `plugins` CLI
(vercel-labs/plugins) can install Supabase into Kimi Code and Grok Build,
alongside the existing Claude Code, Cursor, Codex, Copilot, and Gemini
surfaces.
- Add `.kimi-plugin/plugin.json` for Kimi Code, with the Supabase MCP
server declared inline (X-Source-Name: kimi-plugin) since Kimi reads its
manifest natively and the repo has no root `.mcp.json`.
- Grok Build needs no dedicated manifest: the CLI installs it through
Grok's Claude Code compatibility layer, which reuses `.claude-plugin/`.
- Wire Kimi into the release pipeline: release-please bumps for the
manifest version and the MCP X-Source-Version, and `.kimi-plugin/` is
added to the release tarball.
- Document Grok/Kimi support and the `plugins` CLI in AGENTS.md.
Verified headless with `npx plugins@1.3.4 add <path> --target {kimi,cursor,grok}`:
Kimi and Cursor install cleanly; Grok completes preparation and only fails
on the native `grok` binary being absent from PATH.
Closes AI-926, AI-927, AI-928. Refs AI-925.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…rce file Grok Build natively prefers .grok-plugin/plugin.json over .claude-plugin/ (verified against grok v0.2.101), so it now ships its own manifest pointing at agents/grok/mcp.json with X-Source-Name "grok-plugin" instead of being tracked as "claude-code-plugin". This holds via both `grok plugin install` and the `plugins` CLI, which stages the whole repo. Kimi Code cannot reference an external MCP file — its loader evaluates `mcpServers` as an inline object (Object.entries(manifest.mcpServers)), so a path string breaks. agents/kimi/mcp.json is added as the canonical, tracked source for layout consistency with the other vendors; .kimi-plugin/plugin.json inlines the same block (kept in sync via release-please). - Add .grok-plugin/plugin.json + agents/grok/mcp.json. - Add agents/kimi/mcp.json (mirrors the inline .kimi-plugin block). - release-please: bump versions for .grok-plugin, and X-Source-Version for agents/grok/mcp.json and agents/kimi/mcp.json. - release.yml: add .grok-plugin/ to the release tarball. - Document both vendor MCP quirks in AGENTS.md. Verified end-to-end with the real grok CLI, the kimi CLI package, and `npx plugins@1.3.4`: grok resolves agents/grok/mcp.json (grok-plugin), kimi loads exactly one inline server (kimi-plugin), cursor and claude still install cleanly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Kimi cannot reference an external MCP file (its loader treats mcpServers as an inline object), so a separate agents/kimi/mcp.json was a pure duplicate. Remove it and document Kimi as the explicit exception to the "MCP config lives in agents/<vendor>/" convention in AGENTS.md. The MCP server stays declared inline in .kimi-plugin/plugin.json. - Remove agents/kimi/mcp.json and its release-please X-Source-Version entry. - AGENTS.md: note the Kimi inline exception and that there is intentionally no agents/kimi/mcp.json. Re-verified: `npx plugins@1.3.4 add --target kimi` still loads exactly one MCP server (kimi-plugin). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The new .grok-plugin and .kimi-plugin manifests split between the full 11-keyword list (claude, copilot) and the minimal 5 (cursor, codex). Align both new plugins to the full canonical keyword set used by the flagship .claude-plugin/plugin.json for consistency. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Remove the Grok/Kimi MCP notes block. The plugin manifests remain; the test scaffolding that previously accompanied this change has moved to a dedicated branch/PR. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rodriguespn
force-pushed
the
pedrorodrigues/ai-925-add-support-for-cursor-grok-and-kimi-plugins
branch
from
July 15, 2026 13:34
cd763a4 to
60b8b5b
Compare
Rodriguespn
marked this pull request as ready for review
July 15, 2026 14:20
Collaborator
Author
|
Superseded — split into two focused PRs per review feedback (Grok on hold): Kimi Code support and Grok Build support are now separate. Test scaffolding also lives in its own branch. |
This was referenced Jul 15, 2026
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
1 participant
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.
Summary
Extends the multi-vendor plugin layout so the vendor-neutral
pluginsCLI can install Supabase into Grok Build and Kimi Code, alongside Claude Code, Cursor, Codex, GitHub Copilot, and Gemini CLI.What each vendor needs
.grok-plugin/plugin.json(new)agents/grok/mcp.json(new)grok-plugin.kimi-plugin/plugin.json(new)kimi-pluginWe deliberately keep each vendor's MCP config in a separate
agents/<vendor>/file for consistency and telemetry.Grok plugins supports this structure but Kimi needs an inline MCP config file inside
.kimi-plugin/plugin.jsonmanifest. We can still track kimi's plugin usage.Closes AI-927, AI-928, AI-925.