Skip to Content
Raydo

Develop and package a Raydo plugin

Describe a skills or MCP package with raydo.json, or build a native App Connection archive.

Add Raydo metadata to an existing plugin

Keep your host's manifest in its own directory. Lay out your skill instructions in skills/<name>/SKILL.md, and declare MCP servers in .mcp.json when needed. Add the Raydo-only file alongside the existing manifest:

example-plugin/
  .claude-plugin/plugin.json
  .raydo-plugin/raydo.json
  skills/example/SKILL.md
  .mcp.json

A minimal .raydo-plugin/raydo.json can be:

{
  "schemaVersion": 1,
  "id": "example.documents",
  "displayName": "Example Documents",
  "version": "1.0.0",
  "publisher": { "id": "example", "displayName": "Example" }
}
  • schemaVersion and id are required. Raydo validates the closed schema, and metadata such as display name and version can override the external manifest in the import preview.
  • tools keys use MCP-server-id/tool-name, where the server is in the package. Use read, write, or destructive for the effect. Set approval and idempotency to required on write or destructive operations that require those controls. Declaring an effect does not grant authority.
  • connections declares connector IDs and required capabilities. Direct external imports do not receive the user's Raydo sign-in or connection credentials. Keep secrets in supported credential setup.
  • contributes can describe workflow and role file paths. The external import preview lists those declarations, but does not import those templates at this time.

Ship built MCP entry points and document their local prerequisites. Raydo does not run install scripts or fetch npm dependencies during a link import.

Build a native App Connection archive

Use Node.js 22.12 or later. Use the developer-preview scaffold when you need the native capability contract. The default scaffold is read-only. The local pack command writes dist/plugin.raydo.zip and reports its manifest and package digests.

npm create raydo-plugin@next my-raydo-plugin -- --plugin-id example.documents --display-name "Example Documents" --connector-id notion
cd my-raydo-plugin
npm install
npm run verify
npm run pack

Review the declared schemas, permissions and contract fixtures. Keep the file built by the verified run. Follow distribution and installation to test the appropriate import path with sample data.

On this page

Develop and package a Raydo plugin