You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>
"description": "Official Supabase plugin for Kimi Code with bundled Supabase skills and MCP access for project management, database work, auth, storage, and Postgres best practices.",
Copy file name to clipboardExpand all lines: AGENTS.md
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,12 @@
1
1
# AGENTS.md
2
2
3
-
This repository is the plugin distribution repo for Supabase across Claude Code, Cursor, Codex, and Gemini.
3
+
This repository is the plugin distribution repo for Supabase across Claude Code, Cursor, Codex, GitHub Copilot, Gemini, Grok Build, and Kimi Code.
4
+
5
+
These vendors are installable through the vendor-neutral [`plugins`](https://github.com/vercel-labs/plugins) CLI, which translates the shared plugin layout into each target's native format:
@@ -9,11 +15,14 @@ Keep this repository focused on the shared multi-vendor plugin layout:
9
15
-`.claude-plugin/plugin.json` defines the Claude Code plugin identity and metadata
10
16
-`.cursor-plugin/plugin.json` defines the Cursor plugin surface
11
17
-`.codex-plugin/plugin.json` defines the Codex plugin surface
18
+
-`.kimi-plugin/plugin.json` defines the Kimi Code plugin surface (with its MCP server declared inline)
12
19
-`.github/plugin/plugin.json` defines the GitHub Copilot plugin surface
13
20
-`agents/claude/.mcp.json`, `agents/cursor/mcp.json`, `agents/codex/.app.json`, and `agents/copilot/.mcp.json` hold agent-specific MCP config files
14
21
-`gemini-extension.json` defines the Gemini extension manifest
15
22
-`skills/` contains the shipped, real skill files consumed by the supported plugin surfaces
16
23
24
+
Grok Build does not have its own manifest: the `plugins` CLI installs it through Grok's Claude Code compatibility layer, which reads `.claude-plugin/plugin.json` (and therefore `agents/claude/.mcp.json`). There is no `.grok-plugin/` directory to maintain.
25
+
17
26
This repo should stay self-contained. Claude marketplace installs copy the plugin into Claude's local cache, so paths outside the plugin root are fragile and should be avoided.
18
27
19
28
## Important Commands
@@ -26,7 +35,7 @@ npx claude plugin validate .claude-plugin/plugin.json
26
35
27
36
## Editing Rules
28
37
29
-
- Do not move `skills/`, `agents/`, `.claude-plugin/plugin.json`, `.cursor-plugin/plugin.json`, or `.codex-plugin/plugin.json` out of the repo root layout.
38
+
- Do not move `skills/`, `agents/`, `.claude-plugin/plugin.json`, `.cursor-plugin/plugin.json`, `.codex-plugin/plugin.json`, or `.kimi-plugin/plugin.json` out of the repo root layout.
30
39
- Do not replace `skills/` with a symlink or submodule reference.
31
40
- Keep the plugin name stable as `supabase` unless there is a deliberate migration plan.
32
41
- When changing descriptions or keywords, update all relevant `plugin.json` files together.
@@ -52,6 +61,14 @@ Known vendor documentation pages:
- Installed via the `plugins` CLI using Grok's Claude Code compatibility layer (reuses `.claude-plugin/`); no dedicated manifest.
67
+
- Kimi Code:
68
+
-https://www.kimi.com/code
69
+
- Installed via the `plugins` CLI into Kimi's native plugin store; uses `.kimi-plugin/plugin.json` with skills, commands, hooks, and MCP servers (no agents or LSP support).
70
+
-`plugins` CLI (vendor-neutral installer):
71
+
-https://github.com/vercel-labs/plugins
55
72
56
73
For vendors listed above, read the official documentation pages for the vendor you are working on and follow the plugin structure required by those docs.
0 commit comments