mcp-ikaos-story

Stdio MCP server for creating and modifying iKAOS Story prototype content with Codex or Claude Code.

The MCP talks to the authenticated iKAOS Story API. Users do not need to clone ikaos-content-studio-v2026 or configure a local repository path. Story content/layout JSON lives in Supabase, while fixed workflow documents and source metadata remain read-only behind the API.

Boundaries

• get_story_context returns the current content revision and authoritative docsLink.

• start_story updates the confirmed type, compatible template, source receipt, and start status through the authenticated API; completed Stories are protected.

• save_story_content writes only content_data; source, docs, Story identity, and other production metadata cannot be changed.

• bulk_update_story_status previews and confirms a status-only update for typed Stories. The API writes only status: awaiting_review.

• reset_story always requires a preview token. Confirm archives the complete production row atomically, preserves Story/Sheet/DOCX identity, and clears generated type, template, content, images, route, and revision.

• A Story whose Sheet type/template is set, or whose production is completed/deployed, also requires the exact RESET <story_id> confirmation returned by preview.

• Every content write and reset confirmation is revision-protected. A stale operation returns a conflict instead of overwriting newer content.

• Image generation is out of scope. Designers can upload and replace supplied image files through DF Asset Hub.

• Asset Hub does not currently expose list or delete APIs. Removing an image URL from Story content does not remove its R2 object.

• No Supabase service key is distributed to MCP users.

Related MCP server: Intern MCP

Install

npm install
npm run build

Configure the Story API:

export IKAOS_STORY_API_URL=https://ikaos-content-studio-v2026.vercel.app
export IKAOS_STORY_API_TOKEN=your-project-scoped-api-token

Image uploads use these defaults, so users do not need a df-login token:

export DF_ASSET_UPLOAD_URL=https://df-asset-hub.vercel.app/api/review/figma-images/upload
export DF_ASSET_PROJECT_ID=ikaos-story-2026

Both DF_ASSET_* values are optional overrides. Preview links use IKAOS_STORY_API_URL as their origin. Never commit the Story API token.

Codex

codex mcp add ikaos-story \
  --env IKAOS_STORY_API_URL=https://ikaos-content-studio-v2026.vercel.app \
  --env IKAOS_STORY_API_TOKEN=your-project-scoped-api-token \
  -- node /absolute/path/to/mcp-ikaos-story/dist/src/index.js

The default Asset Hub endpoint and project namespace need no extra Codex env values. Verify with codex mcp list or /mcp.

Claude Code

claude mcp add --transport stdio \
  --env IKAOS_STORY_API_URL=https://ikaos-content-studio-v2026.vercel.app \
  --env IKAOS_STORY_API_TOKEN=your-project-scoped-api-token \
  ikaos-story -- node /absolute/path/to/mcp-ikaos-story/dist/src/index.js

The default Asset Hub endpoint and project namespace need no extra Claude env values. Verify with claude mcp list or /mcp.

Tools

Content workflow

1. Call get_story_context.

2. Open docsLink and read the required fixed rules with get_story_rules.

3. After the user confirms the type and matching template (basic → B-*, immersive → I-*, narrative → N-*), call start_story with both type and template_id. Do not request a local Content Studio checkout.

4. Modify only the returned currentData.data content/layout object. Read-only fields may be omitted, but any supplied values must remain unchanged.

5. Call save_story_content with the unchanged Story ID and the latest currentData.revision. Use null only when the Story has no content yet.

6. Call validate_story, then check the returned preview URL at 390px and 1280px.

If another client saved first, fetch the latest context and merge intentionally. Do not retry with a replaced revision without reviewing the newer content.

Reset workflow

1. Call reset_story with mode: "preview" and the Story ID.

2. Review current, preserved, cleared, protectionReasons, and result.

3. Call reset_story again with mode: "confirm" and the unexpired preview_token.

4. If protected is true, also pass the exact requiredConfirmation string as confirmation.

5. A changed revision or production state invalidates the token. Preview again; never bypass the conflict.

Confirm creates an immutable archive before clearing generated fields in the same database transaction. It does not modify the Sheet or authoritative DOCX receipt and does not delete Asset Hub files.

Image workflow

1. Choose a valid imageSlots[].slotId from the Story content.

2. Call upload_story_image with an absolute local image path.

3. Use the returned imageUrl in the Story content and save it with save_story_content.

4. Call update_story_image with the returned imageId to replace that Asset Hub image. Keep the same file format to reuse the exact R2 key.

5. To stop using an image, remove its URL from Story content and save the new revision. The R2 object remains until Asset Hub adds a delete API.

Omit viewport for one responsive source. Pass the exact same viewport object to update when using separate mobile or desktop files.