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
feat: give Grok a dedicated manifest and MCP config; add Kimi MCP source 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>
"description": "Official Supabase plugin for Grok Build 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
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,17 @@ Keep this repository focused on the shared multi-vendor plugin layout:
15
15
-`.claude-plugin/plugin.json` defines the Claude Code plugin identity and metadata
16
16
-`.cursor-plugin/plugin.json` defines the Cursor plugin surface
17
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)
18
+
-`.grok-plugin/plugin.json` defines the Grok Build plugin surface
19
+
-`.kimi-plugin/plugin.json` defines the Kimi Code plugin surface (with its MCP server declared inline — see below)
19
20
-`.github/plugin/plugin.json` defines the GitHub Copilot plugin surface
20
-
-`agents/claude/.mcp.json`, `agents/cursor/mcp.json`, `agents/codex/.app.json`, and `agents/copilot/.mcp.json` hold agent-specific MCP config files
21
+
-`agents/claude/.mcp.json`, `agents/cursor/mcp.json`, `agents/grok/mcp.json`, `agents/kimi/mcp.json`, `agents/codex/.app.json`, and `agents/copilot/.mcp.json` hold agent-specific MCP config files
21
22
-`gemini-extension.json` defines the Gemini extension manifest
22
23
-`skills/` contains the shipped, real skill files consumed by the supported plugin surfaces
23
24
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
+
Two vendor-specific MCP notes:
26
+
27
+
-**Grok Build** natively prefers `.grok-plugin/plugin.json` over `.claude-plugin/plugin.json` (verified against `grok``v0.2.101`), so it gets its own manifest pointing at `agents/grok/mcp.json` (`X-Source-Name: grok-plugin`). This holds whether it is installed through the `plugins` CLI (which stages the whole repo) or via `grok plugin install`. Grok resolves the `mcpServers` file-path reference.
28
+
-**Kimi Code** cannot reference an external MCP file: its plugin loader evaluates `mcpServers` as an inline object (`Object.entries(manifest.mcpServers)`), so a path string is treated as characters and breaks. `.kimi-plugin/plugin.json` therefore inlines the MCP server. `agents/kimi/mcp.json` is kept as the canonical, tracked source of that block for layout consistency with the other vendors; the two must stay in sync (release-please bumps the `X-Source-Version` in both).
25
29
26
30
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.
27
31
@@ -35,7 +39,7 @@ npx claude plugin validate .claude-plugin/plugin.json
35
39
36
40
## Editing Rules
37
41
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.
42
+
- Do not move `skills/`, `agents/`, `.claude-plugin/plugin.json`, `.cursor-plugin/plugin.json`, `.codex-plugin/plugin.json`, `.grok-plugin/plugin.json`, or `.kimi-plugin/plugin.json` out of the repo root layout.
39
43
- Do not replace `skills/` with a symlink or submodule reference.
40
44
- Keep the plugin name stable as `supabase` unless there is a deliberate migration plan.
41
45
- When changing descriptions or keywords, update all relevant `plugin.json` files together.
@@ -63,10 +67,12 @@ Known vendor documentation pages:
- Uses a dedicated `.grok-plugin/plugin.json` (Grok prefers it over `.claude-plugin/`) pointing at `agents/grok/mcp.json`. Installable via the `plugins` CLI or `grok plugin install`.
67
72
- Kimi Code:
68
73
-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).
- 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). MCP servers must be declared inline — Kimi does not resolve external file references.
0 commit comments