Connect an AI assistant

Your AI assistant can manage pages, layouts, and media on your sites, on your behalf.

It works with apps that support remote MCP connections and Stormy CMS sign-in, including Claude, ChatGPT, Cursor, VS Code, and Devin. Setup and availability depend on the app and your plan.

Add Stormy CMS to your app

The quickest way is from the account portal. Open a site and choose AI assistants.

Or add this server URL to your app:

https://api.stormycms.com/mcp

Claude Code

claude mcp add --transport http stormy https://api.stormycms.com/mcp

Then run /mcp in Claude Code and choose Authenticate.

Run Claude Code in your project's repository. It can then read your components and build pages from them.

Claude on the web and desktop

Choose Add to Claude on your site's AI assistants page. It opens Claude with Stormy CMS filled in. Or set it up yourself:

1. Open Customize, then Connectors.
2. Choose + Add, then Add custom connector.
3. Name it Stormy CMS, paste the server URL, and choose Add.
4. Choose Connect. Sign in to Stormy CMS and approve the sites you want to connect.

The connector also works in the Claude desktop app.

On Team and Enterprise plans, an owner adds the connector under Organization settings, then each member connects to it. Free plans allow one custom connector.

ChatGPT on the web

1. Open ChatGPT Plugins.
2. Use the plus button to choose Add custom MCP server.
3. Name it Stormy CMS, enter https://api.stormycms.com/mcp as the connection URL, and choose OAuth for sign-in.
4. Review the connection warning and choose Create as a plugin. Sign in to Stormy CMS and approve the sites you want to connect when prompted.
5. Install the plugin, start a new chat, and select it by typing @.

The current Plugins setup does not require developer mode. If your account still shows the older Apps settings, follow OpenAI's connection guide for that version. Available actions depend on your ChatGPT plan and workspace permissions. If you cannot add the connection or make changes, ask your workspace administrator to check access.

ChatGPT desktop

1. Open Settings, then MCP servers, and choose Add server.
2. Name it Stormy CMS, choose Streamable HTTP, and paste the server URL.
3. Save, choose Restart, then Authenticate to sign in and approve your sites.

These are the desktop app's local MCP settings. Adding a server here does not also set it up on ChatGPT's website. If these settings are missing in your app, use the web instructions above or check OpenAI's desktop MCP guide.

Codex CLI and IDE extension

If you use Codex from a terminal, add the server and sign in:

codex mcp add stormy --url https://api.stormycms.com/mcp
codex mcp login stormy

In the IDE extension, use MCP servers in the settings menu to add the same URL. Codex CLI, the IDE extension, and ChatGPT desktop share MCP settings when they run on the same Codex host. A connection inside a development container or on another computer is separate.

Cursor

Choose Add to Cursor on your site's AI assistants page. Or add this to .cursor/mcp.json:

{
  "mcpServers": {
    "stormy": { "url": "https://api.stormycms.com/mcp" }
  }
}

VS Code

Choose Add to VS Code on your site's AI assistants page. Or add this to .vscode/mcp.json:

{
  "servers": {
    "stormy": { "type": "http", "url": "https://api.stormycms.com/mcp" }
  }
}

Devin

An organization admin adds a custom MCP server in Devin's settings, using the server URL.

Devin can share one connection with your whole Devin organization. Everyone who uses it acts as you.

Choose your sites

Your app opens Stormy CMS in your browser. Sign in, check the sites the assistant may use, and choose Allow.

When more than one site is connected, the assistant names the site for every change. If it isn't sure which one you mean, it asks.

Ask for what you want

Describe the change in plain words:

Add an About page with a heading and two paragraphs about our team.

Changes go live as soon as they are saved, so your assistant explains each one and asks before making it.

Good to know

Permissions. The assistant can do what you can do on each site, and nothing more.

For example, a contributor's assistant can edit pages but can't create or delete them.

Your components. The assistant builds pages from the components registered in your project.

If your project has components that aren't deployed yet, the live site can't show them. The assistant warns you before using one.

Usage. Each action counts as one API request on the site's plan.

Disconnecting. Remove Stormy CMS from your app. Removing someone from a site disconnects their assistants from it right away.

Troubleshooting

Upload media

With the hosted-media release, assistants can check storage, prepare an upload, transfer the file to its temporary URL, and confirm completion. The tools are get_media_storage, prepare_media_upload, complete_media_upload, and cancel_media_upload.

The same site permissions and storage allowance apply as in the admin. The remote connection cannot read files directly from your computer. Your assistant needs a file-transfer tool; otherwise upload through the admin and ask the assistant to select the uploaded media. See Media storage.