MCP settings Enable MCP sandbox session and Download IDE package
MCP sandbox and bridge

Appifio Creator · Lesson T12 · Technical

Aura MCP:
sandbox · token · bridge

Three MCP ideas people often mash into one. Separate them and you’ll see why the IDE “already fixed” the site while live hasn’t changed - and why you get 403 after ~24 hours.

Goal: Define sandbox / token / bridge; know the 60-day and ~24h limits; follow the required UI order.

Before: H02, T01 · After: K / X series · UI: Enable MCP integration · Save MCP state · Create / resume session · Create token · Revoke · Download Appifio Aura MCP package (.zip)

1. Three-layer diagram

1. Gateway flag - "Enable MCP integration" + "Save MCP state" (public flag; token is not stored here)
2. Sandbox session - "Create / resume session" · IDE AI only reads/writes the sandbox
3. Token API - "Create token" (≤10/session, expires in 60 days, shown in full once)
4. Bridge zip - "Download Appifio Aura MCP package (.zip)" · ~24h lifetime · configure the IDE
Publish live = "Save changes" in Creator (not an MCP button)

2. Glossary

TermMeaningUI label
SandboxTemporary file space for the IDE - not the live site yetEdit sandbox session
TokenKey for the local bridgeCreate token · Revoke · Token label
Bridge / MCP packageZip with bridge runtime, mcp-config examples, and READMEDownload package… (.zip)
Session IDSession identifier; "No session yet" if emptySession ID
Need API key firstMCP depends on the Backend keyno_api_key

3. Steps (required order)

  1. "Backend" tab - have an API key (T06).
  2. "MCP" tab → enable "Enable MCP integration""Save MCP state".
  3. "Create / resume session" (required before token - UI: “Create an edit sandbox session before creating a token”).
  4. Token label (e.g. placeholder Dev machine) → "Create token" → copy immediately.
  5. Enter the extract folder (no spaces) → "Download Appifio Aura MCP package (.zip)".
  6. Configure the IDE with Method A / or Method B escaped paths · Node 18+.
  7. After IDE edits: open Creator → review "Changes""Save changes" to go live.

4. Comparisons · Limits · Security

  • Cursor / Claude MCP servers: same protocol; Appifio adds sandbox → Creator Save.
  • Git remote push: MCP edit ≈ local commit; Save changes ≈ push to production.

You can: use a strong IDE on the sandbox. You cannot: have MCP publish by itself; see the token a second time; keep the bridge forever (~24h).

Security: keep zip/token private; if leaked → "Revoke"; never commit mcp-config with a token to a public repo.

5. Issues · Tips · Series T checklist

IssueFix
403 after a dayDownload the zip package again (~24h)
IDE edited but visitors don’t see itSave changes from Creator
Windows JSON path errorsMethod A with forward slashes /

End-of-series T checklist (T01-T12):

  1. Can you tell virtual disk / live, flat / indexed, Easy / Advanced Soft Storage apart?
  2. Do you know which system files are blocked and when the CMS manifest matters with Aura CMS on?
  3. Do you pick Checkpoint / History / Versions correctly, and know MCP sandbox ≠ live?

End of series T

Suggested next: series K (hands-on) or X (troubleshooting).

Appifio Creator · User guide · T12