Developers · Build with AI
Connect Your AI Assistant to the CLI
Last updated 18 November 2026
Set up Claude Code, Cursor or VS Code to use Insites CloudShell with one command, insites-cli ai init.
insites-cli ai init connects your editor's AI assistant to Insites in one command. It sets up Insites CloudShell, so your AI can deploy and check its work on your sites, and for Claude Code it also adds the insites-aim plugin. This page describes the CLI 6.4.1.
Before You Start
- The Insites CLI 6.4.1 or later. See Getting Started.
- Claude Code, Cursor or VS Code.
- Your project folder open in a terminal.
Run It
- In your project folder, run:
insites-cli ai init - The CLI finds which of Claude Code, Cursor and VS Code are on your computer and asks which to set up. Tick the ones you want.
- For Claude Code, it asks whether to add a short
CLAUDE.mdfile if the project has none. - Restart your editor. The first time your AI uses CloudShell, your browser opens so you can sign in with your Insites account.
What It Writes
| Editor | File | What is added |
|---|---|---|
| Claude Code | .mcp.json | The CloudShell server, https://cloudshell.insites.io/mcp. You sign in through your browser, so no key is stored in the file. |
| Claude Code | .claude/settings.json | The insites-aim plugin and the marketplace it comes from. |
| Claude Code | CLAUDE.md | A short file pointing your AI at the Insites Logic Engine and the site's /admin/api page. Only when the project has none, and only after you agree. |
| Cursor | .cursor/mcp.json | The CloudShell server. |
| VS Code | .vscode/mcp.json | The CloudShell server. |
Every file is merged, never replaced. Other servers and settings stay as they are, and an existing CloudShell entry is updated in place. If a file is not valid JSON, the command stops before it writes anything. Each file is read back after writing to check it. Running the command again reports No changes.
Options
| Option | What it does |
|---|---|
--tool <tool> | The editors to set up: claude, cursor, vscode or all, separated by commas. Skips the question. |
--yes | Ask nothing. Use the editors found, or the ones in --tool. |
--dry-run | Show the changes to each file and write nothing. |
insites-cli ai init --tool claude,cursor --yes
insites-cli ai init --dry-run