# Set up Aixio in your AI agent

Aixio connects to your AI app through one hosted MCP connector. Once it is connected, your agent can work in your Aixio projects through their own Aixio agent, make and edit images and video, turn images into editable layers, edit and run canvases, organize your Aixio library, run your saved automations and design things for it to build (Aixio Design). It uses your existing Aixio account and credits.

Setup is free: it connects, signs you in, installs two skills and checks the connection. It runs no paid jobs.

- **aixio**: what Aixio can do and which tool fits which request, with the rules for credits, uploads and jobs.
- **aixio-design**: the design pipeline: one real design reference → a mockup you review → editable layers → your agent builds it.

Copy the whole block below into Claude Code, Codex, Cursor or another coding agent. For Claude and other chat apps, see "Chat apps" below.

```text
Set up Aixio in this agent: connect the Aixio MCP connector, let me sign in, install the aixio and aixio-design skills, then check the connection without spending credits.

Connector URL (Streamable HTTP, browser OAuth, no API key):
https://data.aixio.app/functions/v1/platform-api-mcp

1. Connect. Look at the existing MCP configuration first and reuse a connection to this URL. Keep unrelated servers. Do not overwrite a different server already named aixio. If it is missing, add it with this host's own mechanism:
   Claude Code: claude mcp add --transport http --scope user aixio https://data.aixio.app/functions/v1/platform-api-mcp
   Codex: codex mcp add aixio --url https://data.aixio.app/functions/v1/platform-api-mcp
   Cursor: in ~/.cursor/mcp.json, under "mcpServers", add
     "aixio": { "type": "http", "url": "https://data.aixio.app/functions/v1/platform-api-mcp", "auth": { "CLIENT_ID": "99521acb-7aa1-476d-9c56-c1936938b015" } }
     The CLIENT_ID is Cursor's registered public OAuth client ID, not a secret; there is no client secret.
   Other hosts: add the URL as a remote HTTP MCP server; if you cannot change MCP settings, tell me exactly where to add it.
   Check the installed CLI's help if the syntax differs. Do not install the older local REST-key packages for this.

2. Sign in. Start the host's browser OAuth sign-in (Claude Code: /mcp, then aixio; Codex: codex mcp login aixio if it did not open; Cursor: Connect next to aixio in MCP settings). Let me finish sign-in and consent in the browser. Never ask me for a password, API key or token in chat. If the host must restart to load the connector, say so and continue the check in the new session.

3. Install both skills, each as <skill folder>/<name>/SKILL.md, from:
   https://aixio.app/skills/aixio/SKILL.md
   https://aixio.app/skills/aixio-design/SKILL.md
   Skill folder: Claude Code ~/.claude/skills; Codex ~/.agents/skills; Cursor ~/.cursor/skills; otherwise the host's documented user-level skills folder. Check each downloaded file has the matching "name:" in its frontmatter. If this host has no skills, add a short, clearly marked Aixio section to this project's agent instructions that links both files, and tell me it only applies to this project. Keep existing instructions. If skills from an earlier Aixio setup are installed (aixio-designer or use-aixio-api), tell me and ask before removing them: the new skills replace them. Do not claim the skills were saved if you could not write them.

4. Check without spending. Confirm the connector is connected and signed in, list the Aixio tools you can see, call balance, and call list_workspaces if it is available. Do not call ask_agent, design, approve_design, design_status, edit_canvas, run_canvas, run_automation or any model tool, and do not upload files. Report what passed, what still needs sign-in or a restart, whether this host can upload local files (needed for images you give Aixio), and where the skills were saved. Writing configuration alone is not a successful setup.
```

## Chat apps

In Claude: Settings → Connectors → Add custom connector. Name it Aixio, paste the connector URL above and connect. Other chat apps: use their remote MCP connector settings with the same URL. Chat apps without skills still get the tools and the connector's own instructions; you can paste the two skill files into a project's instructions if the app supports that.

## After setup

Ask in your own words. The skills pick the route; you can also call them by name: `/aixio` and `/aixio-design` in Claude Code (from the Claude plugin: `/aixio-api:aixio` and `/aixio-api:aixio-design`), `$aixio` and `$aixio-design` in Codex.

- "In my Aixio canvas *Spring launch*, make three product shots in the amber skill's style."
- "Turn this poster into editable layers."
- "Make a 5-second video from this image."
- "Tag my uploaded product photos by colour and put them in a *Catalog* collection."
- "Design a landing page from these product photos and build it in this React project. Show me the mockup first." (aixio-design)
- "Make a 10-slide pitch deck as a PPTX in our brand." (aixio-design)

Every paid step is agreed with you first. Disconnect at any time from https://aixio.app/developers?tab=connections.

Guides: [MCP quickstart](https://aixio.app/mcp/) · [Aixio Design guide](https://aixio.app/mcp/design/). Installation syntax follows the [Claude Code MCP](https://code.claude.com/docs/en/mcp), [Codex MCP](https://developers.openai.com/codex/mcp) and [Cursor MCP](https://cursor.com/docs/context/mcp) documentation.