Package structure and manifests

​

Directory layout

sales-board/
├── .minimax-plugin/
│   └── plugin.json          # plugin manifest
├── package.json             # only the mcode extension is needed
├── icon.png
├── servers.mcp.json         # optional
├── skills/                  # optional
└── miniapp/
    ├── miniapp.json         # MiniApp declaration
    ├── client/              # page payload
    │   ├── index.html
    │   └── client-api.ts    # optional: type checking only
    └── node/                # Node payload
        ├── server.mjs
        └── miniapp-api.ts   # optional: type checking only

​

Plugin manifest: plugin.json

{
  "schemaVersion": 1,
  "name": "sales-board",
  "displayName": "Sales Board",
  "version": "1.0.0",
  "description": "Shows the verified sales pipeline.",
  "author": "Your Name",
  "icon": "icon.png",
  "category": "Business",
  "exampleQueries": ["Open my sales pipeline dashboard."],
  "apps": [],
  "mcpServers": [],
  "skills": []
}

• name is a lowercase machine name of up to 80 characters that starts with a letter and may use digits and . _ - as separators. It is the Mini App’s pluginId.
• version uses SemVer. description, author, and every exampleQueries entry must be non-empty.
• icon points to a PNG, JPEG, or WebP inside the package. init provides a default icon.
• apps, mcpServers, and skills keep their ordinary plugin meaning; use empty arrays for capabilities you don’t have.

​

Entry declaration: package.json

{
  "mcode": {
    "schemaVersion": 2,
    "miniApp": "./miniapp/miniapp.json"
  }
}

​

Mini App declaration: miniapp.json

{
  "schemaVersion": 1,
  "artifacts": {
    "client": ["./miniapp/client"],
    "node": ["./miniapp/node"]
  },
  "runtime": {
    "kind": "process",
    "entry": "./miniapp/node/server.mjs",
    "lifecycle": "on-demand"
  },
  "surface": {
    "path": "/dashboard",
    "window": { "width": 960, "height": 700, "resizable": true }
  },
  "mcpEndpoints": [],
  "hostConnectorAccess": { "providers": ["notion"] },
  "agentAccess": ["session.run"],
  "agentConcurrency": 4
}

• artifacts.client and artifacts.node are both required. They define what the host hashes, adopts, and publishes; they can be source directories rather than build output, and they may overlap.
• runtime.entry is the Node entry, ending in .js, .mjs, or .cjs, inside the Node payload. lifecycle is always on-demand: enabling or scanning a plugin never starts the service.
• surface.path is the page route served by the Node service.
• hostConnectorAccess and agentAccess are explicit grants; leave them out and you don’t get them. Declare them only when the runtime really needs them.

​

Payload rules

• The host doesn’t install dependencies or run builds. Ship something ready to run, and bundle or vendor third-party runtime dependencies into a payload directory. Prefer Node built-ins and browser APIs.
• node_modules is build state: it is never published and must not sit inside a declared payload.
• Use portable relative paths: no absolute paths, .., backslashes, or symlinks, and nothing outside the package.
• Every file in a payload except node_modules goes into the digest. Delete logs, caches, temporary files, and anything else you don’t want published before you publish.