Connect Claude Code to your store’s themes in two steps: add the remote MCP server, then sign in.

Before you start

  • A PlatformDTC account with access to the store whose theme you want to build.
  • Claude Code installed.

1. Add the server

This adds the server for you in the current project. Add --scope user to make it available in every project, or --scope project to share it with your team through the project’s .mcp.json.

2. Sign in

Start Claude Code and run:
Select platformdtc-theme and choose to authenticate. Your browser opens PlatformDTC:
1

Sign in to PlatformDTC

If you are not signed in already, sign in with your PlatformDTC account.
2

Review the request

The consent screen shows the client that is asking (Claude Code), where it will return you, and the permissions it requests: read_themes, write_themes and, if requested, publish_themes.
3

Choose a store and permissions

Pick the store this connection is for. You can untick any permission you do not want to grant — for example leave publish_themes off, and your agent can build and preview but never publish.
4

Approve

You return to Claude Code, which now lists the theme tools.
Claude Code stores the tokens and refreshes them itself. The access it holds is bound to the one store you chose and to the permissions you granted. See OAuth for what is issued.
You can also sign in from the command line with claude mcp login platformdtc-theme, on Claude Code versions that include it.

3. Build

Ask for what you want in plain language. For example:
The server tells the agent the working loop — manifest, read, write, check, preview, publish — so it will:
  1. call create_dev_theme and get_theme_manifest to see the files and section types,
  2. read templates/index.json with read_theme_files,
  3. write the change with write_theme_files, or a custom section when no existing section fits,
  4. run check_theme and fix what it reports,
  5. return a preview_theme link you can open.
Open the link, and open the theme in the dashboard editor — the change is already there.

4. Publish

When you are happy with the preview, ask the agent to publish. With the default store setting the publish waits for your approval and the tool returns pending_approval; approve it in Settings → Developer → Build with your agent and the theme goes live. See Scopes and approvals.

Troubleshooting

  • The tools do not appear — run /mcp and check that platformdtc-theme is connected and authenticated.
  • A write is refused — see Troubleshooting for PLATFORM_OWNED, CONFLICT and CHECK_FAILED.