Insites AI · Build with AI in your editor
CloudShell MCP
Last updated 22 November 2026
Connect your AI tool to your sites so it can deploy, read logs and manage settings.
What CloudShell is
CloudShell is a remote MCP server run by Insites. MCP (Model Context Protocol) is the open standard that lets an AI tool use outside tools. When you add CloudShell to your AI tool, the tool can deploy code, upload assets, read logs and manage settings on your Insites sites.
You describe what you want in plain language, and your AI picks the right tool. CloudShell is for developers who build with their own AI tool. People who run a site use the AI features in the admin instead. See MCP tooling for Insites AI for how the two fit together.
How to connect
- Add CloudShell to your AI tool as a remote MCP server, using this address:
https://cloudshell.insites.io/mcp - Sign in with your Insites account when the tool asks. Your browser opens, and you sign in with the same account you use for the Console.
- Ask your AI to list your sites, then select the one you want to work on.
No password or key goes into any settings file. CloudShell acts as you, with the access you have in the Console. The steps for adding a server differ by tool. See Claude, ChatGPT, Gemini, Grok and Cursor.
What it can do
- Deploy code. Pages, partials, layouts, GraphQL, schema and every other file in your codebase.
- Upload assets. Images, fonts, PDFs, and audio and video up to 100 MB. You get the public address back.
- Connect GitHub. Commit your AI's work to a repository, and deploy on every push through the Insites GitHub App.
- Show what happened. Deploy status, deployment history and your site logs.
- Manage settings. Environment variables, and the list of installed modules. Variable values are hidden when your AI lists them; it sees a value only when it asks for that variable by name.
Every change CloudShell makes also appears in the Console change log, with who made it. Small files are sent directly. Large files go through a one-time upload link, and their contents are checked before they deploy.
Claude and ChatGPT on the web cannot run the upload command. There, your AI deploys a file that is already at a public https address, and CloudShell fetches it for you.
Roles you need
What your AI can do follows your role on the site. By default:
| Role | What your AI can do |
|---|---|
| Viewer | Read logs and history |
| Editor | Also set environment variables and push to a branch |
| Developer or above | Also deploy |
If a tool is refused, ask the account owner to change your role in the Console.
Work on one site at a time
Each AI session keeps its own selected site. Two sessions can work on two sites at once. Every result names the site the tool acted on, so you can check that it is the one you meant. See Working on Several Sites.
Tip
Give your AI the Insites Logic Engine as well. CloudShell lets it deploy. The Logic Engine teaches it how to build the Insites way.
Your data
CloudShell receives only what your AI tool sends when it uses a tool, never your conversation. See section 24 of the Privacy Policy for what CloudShell keeps, for how long, and how to ask for it to be deleted.