Insites AI · Build with AI in your editor
Tutorial: Deploy a Page with Grok
Last updated 22 November 2026
Connect Grok to CloudShell and deploy your first page, step by step.
What you will do
This tutorial takes you from nothing to a live page on your Insites site, using Grok on the web. You connect Grok to CloudShell, choose a site, ask for a page, and check that it is live. It takes about 15 minutes.
For the background, see Use Grok with Insites and CloudShell MCP.
Before you start
- An Insites account. The same one you use to sign in to the Console.
- A site, with the Developer role or above on it. A lower role can read logs but cannot deploy. Use a staging site for your first try.
- A Grok account. On a Business or Enterprise workspace, an admin may need to add the connector for you first.
- Grok in a web browser at grok.com.
Step 1: Add CloudShell as a connector
- Open grok.com, sign in, and go to grok.com/connectors.
- Click New Connector, then Custom.
- Enter the MCP server address:
https://cloudshell.insites.io/mcp.
Grok changes its menu names from time to time. If a name here does not match, look for the place where you add a custom connector or an MCP server. Do not paste a password, API key or site ID anywhere. CloudShell does not need one.
Step 2: Sign in with your Insites account
- Grok opens an Insites sign-in window.
- Sign in with your Insites account, the same way you sign in to the Console.
- Approve the access request. The window closes and Grok lists the CloudShell tools.
CloudShell now acts as you, with the same access you have in the Console.
Step 3: Give Grok the Logic Engine
The Insites Logic Engine is the public set of rules for building on Insites. Paste this as your first message in a new chat:
Before you write any code for this project, read the Insites Logic Engine at
https://github.com/insites-io/insites-logic-engine
Start with skills/insites/SKILL.md and follow its decision trees, then use the
reference docs in skills/insites/references/ and the rules in logic-engine/rules/.
Whenever you are unsure how something works on Insites, check the Logic Engine
first instead of guessing, and follow its conventions over your own assumptions.Step 4: Choose your site
Send this, with your own site name:
List my Insites instances, then select the one called my-staging-site.Grok asks you to approve each CloudShell action. Read what it is about to do, then approve it. Check that the reply names the site you meant. Every later result names the site too.
Step 5: Ask for a page and deploy it
Send this:
Create a page at /hello with a heading that says Hello from Grok and one short
welcome paragraph. Save it as app/views/pages/hello.liquid and deploy it to the
selected instance with insites_deploy. Then check the deploy status and the logs.Grok writes the file and sends it to CloudShell, which deploys it. Approve the deploy when Grok asks.
How the file gets there. Grok on the web cannot read files on your computer, so it writes the page content straight into the deploy. That works well for pages and partials of normal size. For a large file, such as an image or a long script, host it at a public https address and ask Grok to deploy it with insites_deploy_from_url. Only use a public address for content anyone may read, and never put a secret in it.
Step 6: Check it is live
- Read Grok's reply. It should show the deploy status as success and no errors in the logs.
- Open your site address with
/helloon the end, for examplehttps://my-staging-site.example.com/hello. - You should see your heading and paragraph.
If the page does not appear, ask Grok: Check the logs on the selected site for errors and fix them.
Step 7: Undo a change
When a deploy replaces a file that was already there, CloudShell keeps a copy of the old file for 30 days. To roll back, ask Grok:
Show my recent deployments on the selected instance and restore the previous
version of app/views/pages/hello.liquid.To remove the test page, ask Grok to delete app/views/pages/hello.liquid. Every change also shows in the Console change log, with who made it.
If something goes wrong
- A tool is refused. Your role on that site is too low. Ask the account owner to give you the Developer role in the Console.
- The wrong site changed. Ask Grok which site is selected before you deploy. See Working on Several Sites.
- Grok does not use CloudShell. Check the connector is connected at grok.com/connectors (Step 2).
- The sign-in has expired. Open the connector at grok.com/connectors and connect again.
- Grok keeps making the same mistake. See When your AI gets stuck.