Let an AI agent work on the same screenshot projects

What MCP actually gives an agent

MCP is an open protocol that lets AI clients like Claude, Cursor, and Codex call a defined set of tools on a remote server, instead of guessing at your product through screen scraping or a generic HTTP API. StoreStage runs a remote, OAuth-protected MCP server at https://mcp.storestage.studio/mcp. Your client authenticates as you, then calls the tools listed below — nothing more. The full catalog is 23 tools; the ones a client sees depend on the scopes you grant it, and the App Store Connect tools need their own scope.

Every tool an agent can call

Six groups, 23 tools in the full catalog. Reads never return screenshot pixels or file bytes. Editing a project's scene is always preview-then-apply; creating a project or attaching an asset is a one-shot write with its own quota or revision check. Rendering and exporting only read the project's current state — they never modify it.

Set-scoped operations — changeTheme, updateSet, reorderSlides, updateOutputCopy, layer operations, and screenshot/custom-image assets.attach binds — accept an optional setId. When omitted, they act on the device's currently active set. Passing setId directly lets you target any set in the project without needing a preceding selectSet:

[
  {
    "type": "updateOutputCopy",
    "payload": {
      "device": "iphone",
      "setId": "<target setId>",
      "index": 0,
      "patch": { "headline": "New Headline" }
    }
  }
]

To change several outputs at once, updateOutputCopy accepts a list of indexes ([0, 1, 2]) or "all" in place of a single index. Each output becomes its own operation and counts against the 30-operation limit. "all" skips outputs the patch cannot change (for example a panel without a label slot) and lists them in a warning; a list fails on the first such output.

You can also target specific sets directly in assets.attach by including setId in the bind payload without needing to switch the active set first:

{
  "projectId": "<projectId>",
  "expectedRevision": <the project's current revision>,
  "ticket": "<ticket from assets.create_upload>",
  "bind": { "target": "screenshot", "device": "iphone", "index": 0, "setId": "<target setId>" }
}

When setId is omitted, operations continue to act on the active set as before. You can still use selectSet in changes.preview when you want to switch which set is active in the studio.

Fast drafting with projects.draft_from_brief

Instead of executing multiple sequential tool calls to create a project, choose a theme, format copy per slide, and bind screenshots, you can call projects.draft_from_brief in one step. It produces a populated project draft and stages a reviewable changeSetId:

{
  "name": "HabitPulse",
  "description": "Daily habit tracker. Track your streaks, visualize weekly completion stats, and share milestones with accountability partners.",
  "clientRequestId": "req-habitpulse-001"
}

Theme layout models: connected vs. panel

Themes in the StoreStage catalog advertise a kind property that defines their visual layout model:

• Connected ("connected"): The theme is a continuous panoramic strip where artwork and composition span across panel seams. Changing one panel's copy length or layer placement affects the visual balance of the entire strip. StoreStage emits a connected_strip_rhythm warning during preview when copy or layers in a connected set are modified so agents can preserve overall balance.
• Panel ("panel"): Panels are visually independent. Each panel has its own standalone background and composition, allowing copy and layers to be edited on one panel without affecting neighboring panels.

Locale sets & AI translation (Pro)

StoreStage Pro accounts can organize screenshot sets by BCP 47 locale (e.g. "en-US", "de-DE", "ar-SA"). Sets carry an optional locale property, enabling multi-language App Store screenshot localization with full support for Left-to-Right and Right-to-Left (RTL) typography, auto font-shrink scaling, and Arabic script fallbacks.

The sets.translate tool stages an AI translation of any set directly into a target locale:

{
  "projectId": "<projectId>",
  "sourceSetId": "<source setId>",
  "targetLocale": "de-DE",
  "targetSetName": "iPhone - German",
  "clientRequestId": "trans-de-001"
}

Like scene edits, sets.translate returns a preview change set with a changeSetId and diff. Review the staged translated copy and apply with changes.apply.

Designed for reviewable changes

• OAuth connection. Do not paste a StoreStage API key into chat — clients authorize in a browser tab.
• Preview, then apply. Editing a project's scene uses typed change sets checked against the project's current revision, so a stale agent cannot silently overwrite newer work. Attaching an asset carries the same revision guard; rendering and exporting only read the current state and never modify it.
• Assets stay out of tool messages. Files move through short-lived signed upload and download URLs, never as base64 in a tool call.
• One authorization model. The UI, automation API, and MCP tools enforce the same account permissions and Pro entitlements.

Connect your AI client

Remote MCP is included with Pro. Every client below points at the same endpoint — https://mcp.storestage.studio/mcp — and supports OAuth Dynamic Client Registration, so you never need to create or paste a client ID by hand.

claude plugin marketplace add bahadirarslan/storestage-plugins
claude plugin install storestage@storestage-plugins --scope user

{
  "mcpServers": {
    "storestage": {
      "url": "https://mcp.storestage.studio/mcp"
    }
  }
}

codex plugin marketplace add bahadirarslan/storestage-plugins
codex plugin add storestage@storestage-plugins

codex mcp add storestage --url https://mcp.storestage.studio/mcp
codex mcp login storestage

https://mcp.storestage.studio/mcp

{
  "servers": {
    "storestage": {
      "type": "http",
      "url": "https://mcp.storestage.studio/mcp"
    }
  }
}

{
  "mcpServers": {
    "storestage": {
      "serverUrl": "https://mcp.storestage.studio/mcp"
    }
  }
}

{
  "mcpServers": {
    "storestage": {
      "type": "streamableHttp",
      "url": "https://mcp.storestage.studio/mcp"
    }
  }
}

{
  "context_servers": {
    "storestage": {
      "url": "https://mcp.storestage.studio/mcp"
    }
  }
}