Merchant Center Custom Application, zero to nav

End state: a Custom Application on a static host, registered in the user's Organization, Ready, installed in every Organization the user chose (all projects, or an allowlist per Organization), and in those Projects' main menu.

Assumed: the user has a commercetools Project and is in the Administrators Team of an Organization. "Nothing configured" means no custom app yet, not no account. No Project: stop and say so.

How this skill works

The procedure lives in scripts/, not here. Registration is a dozen order-dependent calls, and its failures (wrong applicationId in the build, URL mismatch, Draft state) show up far from their cause. So the scripts read the real Merchant Center state, pick the next step, and act. A rerun after any interruption resumes. Your job: gather inputs, run the scripts in order, and handle what scripts cannot: the email click and, with deployment help off, the deploy.

Every script prints JSON. Read ok, error, stoppedAt, and checks[].detail; never assume a step worked. Run them as node <skill-dir>/scripts/<name>.mjs.

The scripts carry the procedure; the Merchant Center facts around it (what an entryPointUriPath may be, which permissions a Team needs, what a host must do) come from the documentation, so:

1. Docs search (required, run first) — The first time you use this skill in a session you must run this before answering. It gathers the latest verified documentation as your primary grounding, filtered to the products this skill covers. Use this script for documentation search while working with this skill; the Knowledge MCP covers everything else. Always confirm details against retrieved documentation rather than the skill text alone: