Skip to content

Insites AI · Build with AI in your editor

MCP tooling for Insites AI

Last updated 20 November 2026

Connect your own AI assistant to Insites through CloudShell and the Logic Engine.

What MCP tooling is

MCP (Model Context Protocol) is the open standard that lets an AI assistant use outside tools. Insites gives your own AI assistant two things through it:

  • Insites CloudShell, a remote MCP server. It connects an assistant such as Claude Code or Claude Desktop to your Insites sites. The assistant can then deploy files, read logs, manage environment variables and work with a connected GitHub repository.
  • The Insites Logic Engine, the public rules for building on Insites. Your assistant reads it so the files it writes follow Insites conventions.

When to use it

You want toUse
Ask about your data, change a page or record from the admin, or run automationsInsites AI in your site admin. See Chatting with Insites AI
Build or change a site from your own code editor or AI assistantCloudShell, through MCP
Make your own assistant follow Insites rulesThe Logic Engine

Insites AI itself also reads the Logic Engine before it writes a site file. So a page built in the admin and a page built through CloudShell follow the same rules.

Worked example: connect Claude Code and deploy a page

  1. Add CloudShell to your MCP settings, for example in a project .mcp.json file:

.mcp.json

{
  "mcpServers": {
    "cloudshell": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://cloudshell.insites.io/mcp",
        "--transport",
        "http-only"
      ]
    }
  }
}
  1. Start your assistant. On first connect, your browser opens and you sign in with your Insites account.
  2. Ask your assistant to list your sites. It calls insites_list_instances, which shows the sites connected to your account and which one is selected.
  3. Ask it to select the site you want. It calls insites_select_instance. Every deploy, log and settings tool then works on that site until you change it.
  4. Describe the page you want. Your assistant writes the file, reading the Logic Engine for the rules it needs.
  5. Ask it to deploy. A small file goes through insites_sync_file or insites_deploy.
  6. Ask it to check the logs with insites_get_logs, then open the page on your site.

For the full setup in each assistant, see About CloudShell.

The tools, by group

GroupTools
Site selectioninsites_list_instances, insites_select_instance
Deployinsites_deploy, insites_sync_file
Large filesinsites_request_upload, insites_commit_upload, insites_deploy_from_url, insites_deploy_status, insites_upload_asset
Site managementinsites_get_logs, insites_module_list, insites_env_get, insites_env_add
Deployment historyinsites_deployments, insites_deploy_stats
GitHubinsites_github_connect, insites_github_status, insites_github_disconnect, insites_github_tree, insites_github_pull, insites_github_pull_batch, insites_github_push, insites_github_push_branch, insites_github_update_branch, insites_github_commits, insites_github_revert, insites_github_list_deployments

Which tools you can use follows your role in the Console. A tool your role does not allow is refused.

How Insites AI and CloudShell work together

  • A change confirmed in Insites AI is written straight to the site. It does not reach a Git repository on its own.
  • If your team deploys from a repository, pull those changes into it first, or a later deploy may overwrite them.
  • Owners can turn on Write a Commit Message for Every Applied Change under AI > Configuration > General. Each applied change then carries a commit message naming the question, the administrator and the model, which the GitHub connector uses.

Limits

  • The direct deploy tools send file contents through the assistant, so use them for small text files, under about 32 KB. Use the upload tools for anything larger.
  • You see only your own connected sites. One person never sees or uses another person's connections.
  • The --transport http-only setting is required.

Troubleshooting

What you seeWhyWhat to do
The assistant cannot connect to CloudShellThe transport setting is missingAdd --transport and http-only to the args, as above
A tool asks you to select a siteMore than one site is connected and none is selectedAsk the assistant to list, then select, a site
A large file arrives cut shortIt was sent through a direct deploy toolAsk the assistant to use the upload tools
A tool is refusedYour Console role does not allow itAsk an account owner to change your role
A change made in the admin disappeared after a deployThe deploy came from a repository that did not have the changePull admin changes into the repository before you deploy

Note

MCP tooling is for developers. People who run the site use Insites AI in the admin instead.

Related