Some organizations restrict which external services AI tools are allowed to connect to. If your environment doesn't permit MCP connections, you can still use your AI tool to build and edit interactives in Studio.
When MCP is connected, your AI tool automatically has Mighty's documentation and your interactive's code in context. Without it, you provide that context yourself and the result is the same: your AI writes or edits the code, and you bring it into Studio.
This step creates a reusable skill in your AI tool so you don't have to re-explain the Mighty workflow in every conversation. You only need to do this once per tool.
Start a new conversation and paste the prompt below. Your AI tool will set up the skill and walk you through installing it.
Everything here should become a reusable skill in the tool you are running in (as a skill, custom instructions, rules file, or whatever your tool calls it).A .zip will be supplied and describe an edit as my next step. For now, help me set up the skill.What you need to do:1. Briefly confirm you're ready (name the tool you are running in).2. Create a `build-mighty-interactive` skill using the Build instructions below, and walk me through how to install it.## Skill package- **Name**: build-mighty-interactive- **Purpose**: Build and edit Mighty Studio interactives from .zip templates- **Contents**: the Build instructions section below- **Install**: tool-specific steps you determine## Build instructions (include these in the skill)When building or editing interactives in future sessions, follow this:## How you build interactivesBefore writing or changing code, fetch and read:<https://mcp.designwithmighty.com/docsStart> with essentials.md, then other linked docs as needed. Apply conventions from those docs (onSdkReady, getState, formElements in mighty-form-config.json, markAsComplete, common-mistakes guidance, etc.).## Per-edit workflow1. The user provides a Studio template .zip (Download code) or a clear spec from scratch.2. You edit or build; output a .zip with index.html at the root (not in a subfolder).3. The user uploads the .zip via Import code in Studio.## When MCP is not availableIf the user pastes a Studio prompt that references Mighty MCP tools (especially `checkout_interactive` with an `interactiveId`) but you are not connected to the Mighty MCP server and connecting is not an option in this session:- Do not attempt MCP calls or suggest connecting to Mighty MCP.- The template name and interactiveId in their message still identify which interactive they mean; you just cannot fetch files via MCP.- Instead, tell them to download the .zip from an existing interactive in Studio or ask you to start from scratch by creating a folder with index.html at the root, following the docs above.
<aside> 💡
Your AI tool will confirm which tool it's running in and give you tool-specific installation steps. Follow those steps before moving on.
</aside>
Once the skill is installed, use this process for every interactive you build or edit:
Step 1: Download your interactive from Studio
In Studio, open the interactive you want to edit and click Download code. This saves a .zip file to your computer. If you're starting from scratch, you can skip this step.
Step 2: Start a new conversation
Open your AI tool and start a new conversation. The skill you installed will automatically apply — you don't need to paste any setup instructions again.
Step 3: Share the .zip and describe your edit
Upload the .zip file to your conversation and describe what you want to change. Your AI tool will read the Mighty documentation, edit the files, and return an updated .zip with index.html at the root.
Step 4: Import the updated .zip into Studio
In Studio, click Import code and upload the .zip your AI returned. Studio will render a preview so you can check that everything looks right before saving.
Step 5: Iterate in the same conversation
If something needs adjusting, describe the change in the same conversation thread. Your AI tool already has the context from earlier in the session, so you don't need to re-upload the original — just describe what to fix and upload any new .zip it returns.