Dreamboard plugin

Use Codex, Claude Code, or Cursor to find your synced Studio projects, edit card data and customise game code. The plugin shares one skill and remote MCP endpoint across the three hosts. The portable configuration uses streamable-http; Claude and Cursor's native configuration uses their http spelling. It contains no credentials or local server.

The hosted MCP endpoint and its OAuth integration must be deployed before sign-in works. Shipping these plugin files alone does not enable the backend. Installation also does not publish the plugin to any host's public directory.

Install

Codex

Add this repository as a marketplace, then install Dreamboard from that marketplace:

codex plugin marketplace add dreamboard-games/dreamboard-sdk
codex plugin add dreamboard@dreamboard-games

The repo catalog lives in .agents/plugins/marketplace.json; Codex reads the portable plugins/dreamboard/plugin.json manifest. The desktop app can also use the repo marketplace through its Plugins directory.

Claude Code

In Claude Code v2.1.275 or later, run:

/plugin install dreamboard --marketplace dreamboard-games/dreamboard-sdk

Review the plugin and choose its installation scope. Older clients can run /plugin marketplace add dreamboard-games/dreamboard-sdk, then /plugin install dreamboard@dreamboard-games.

Claude uses .claude-plugin/marketplace.json and the plugin's Claude manifest.

Cursor

The repository includes .cursor-plugin/marketplace.json and a Cursor plugin manifest for marketplace distribution. Until it is available in Cursor's public marketplace, add this remote server in Cursor's MCP settings:

{
  "mcpServers": {
    "dreamboard": {
      "url": "https://api.dreamboard.games/mcp"
    }
  }
}

Install the Dreamboard skill into your agent's skill directory as described in Cursor's skills documentation. This uses the same server and instructions as the packaged plugin. Do not add API keys or tokens to the configuration. Complete the browser sign-in when prompted.

The setup cards in Studio's Settings → MCP → Connect your tools provide these instructions and an Add MCP to Cursor install link. That shortcut installs the connection only; install the skill separately or use the full plugin once listed. A setup click is not proof of a connection: complete Dreamboard sign-in and consent.

Use

Try “Find my Dreamboard projects” or “Help me customise this Studio game.” Only actively synced projects are available; free accounts can sync one project. Device-only projects still work in Studio. Use Settings → Manage sync to choose which project to connect.

Reading uses the latest saved cloud revision. Card edits are validated and saved directly to the synced project, even while Studio is closed. Concurrent changes are checked against the saved revision. Each edit has a seven-day recovery receipt; reverting writes a new revision and refuses to overwrite subsequent edits. This recovery is separate from the editor's local Undo. Game code uses a private project repository and temporary, repository-scoped Git credentials. Credentials expire after one hour and must be renewed through the connection tool. Never paste a token into a remote URL or commit it.

Access can be revoked in Studio's Settings → MCP. Disabling project sync stops new remote authoring access; already issued Git credentials expire at their normal expiry.

Maintainer checks

claude plugin validate plugins/dreamboard
claude plugin validate .claude-plugin/marketplace.json

Validate plugin.json and mcp.json against their declared Agent Plugins JSON schemas. Check all three catalog paths, then test sign-in and tool use in each host against a deployed test backend before release. Local manifest validation does not prove OAuth or Git permissions.

Format references: Codex plugins, Claude plugins, Cursor plugins.