Insites AI · Build with AI in your editor
Use Gemini with Insites
Last updated 22 November 2026
Add CloudShell to Gemini CLI and deploy to your site.
Connect Gemini to Insites
Copy this command and run it in your project folder. Then sign in with your Insites account.
gemini mcp add --transport http -s user insites-cloudshell https://cloudshell.insites.io/mcpHaving trouble? See If you have trouble.
Get started in four steps
- Connect. Run the command above. Start Gemini CLI, trust the folder when it asks, and type
/mcp auth insites-cloudshell. Your browser opens. Sign in with your Insites account. - Give it the Logic Engine. Paste this at the start of your project, so Gemini builds the Insites way:
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. - Test it. Copy this into Gemini. It lists your sites, and you pick the one to work on.
List my Insites sites. - Start building. Try this:
Build a homepage with a heading and a short welcome paragraph, and deploy it.
If you have trouble
What you need
- An Insites account and a site. To deploy, you need the Developer role or above on it.
- Gemini CLI, installed and signed in to your Google account.
- The CloudShell address,
https://cloudshell.insites.io/mcp.
Connect Gemini CLI step by step
- In your project folder, run the command in the box at the top of this page.
-s useradds CloudShell for every project. Leave it out to add it to this project only. - Start Gemini CLI with
gemini. If it asks whether you trust this folder, choose to trust it. Gemini turns off every MCP server in a folder you have not trusted. - Type
/mcp auth insites-cloudshell. A browser window opens. Sign in with your Insites account. - Type
/mcp listto check thatinsites-cloudshellis connected.
No password, key or site ID goes into Gemini. CloudShell acts as you, with the access you have in the Console.
Add it to settings.json by hand
With -s user, the command writes to ~/.gemini/settings.json. You can add the server yourself instead, next to any other servers:
- Under
mcpServers, add a server calledinsites-cloudshell. - Give it
urlset tohttps://cloudshell.insites.io/mcpandtypeset tohttp.
See the Gemini CLI MCP guide.
Keep the Logic Engine prompt for every chat
Gemini CLI reads a file called GEMINI.md in your project folder and sends it with every prompt. Put the Logic Engine prompt from step 2 in that file, so you do not need to paste it each time. Type /memory show to check what Gemini has loaded.
Use the Gemini app instead
The Gemini app on the web can add a custom MCP server through Gemini Apps Developer Mode. It is a developer feature and may not be on your account. If you have it, create a new app, enter the CloudShell address and choose Dynamic Client Registration to sign in. The menu names belong to Google and can change, so follow Google's own help. Like any web chat, the Gemini app cannot read the files on your computer.
Common problems
- The server shows as Disabled. You have not trusted this folder. Gemini turns off MCP servers in untrusted folders. Restart Gemini CLI in the folder and trust it.
- The server shows as Disconnected. You have not signed in yet. Type
/mcp auth insites-cloudshell. - You are signed out. Type
/mcp auth insites-cloudshellagain. - A tool is refused. Your role on that site does not allow it. Deploying needs the Developer role or above.
- Gemini asks before each action. That is expected. You can allow a tool, and you can remove CloudShell with
gemini mcp remove insites-cloudshell.