Aixio documentation · Updated October 27, 2026

Aixio MCP quickstart

Connect Claude, Codex, Cursor and compatible AI apps to Aixio with OAuth, then verify the connection without spending credits.

Aixio MCP connects your AI app to Aixio workspaces, media tools and Designer. Use the hosted remote MCP connector with Streamable HTTP and browser OAuth sign-in. No REST API key is needed.

1. Add the MCP server

Paste this exact server URL into your app’s remote MCP connector settings:

https://data.aixio.app/functions/v1/platform-api-mcp

Signing into aixio.app in a browser does not, by itself, authorize an MCP connection. Your AI app must support remote MCP over HTTP and OAuth. Availability and settings names vary by app and plan.

Claude

Open Settings → Connectors → Add → Add custom connector. Name it Aixio, paste the server URL, then continue and connect.

Claude Code

claude mcp add --transport http aixio https://data.aixio.app/functions/v1/platform-api-mcp

In Claude Code, run /mcp, choose Aixio and sign in.

Codex

codex mcp add aixio --url https://data.aixio.app/functions/v1/platform-api-mcp

Codex detects OAuth and starts browser authorization automatically. If sign-in does not open or authorization did not finish, run codex mcp login aixio. Once authorization succeeds, you do not need to log in again. These are terminal commands for Codex CLI; a chat without terminal or connector-management access cannot execute them for you.

Cursor

Add the following to your MCP configuration, then select Connect next to Aixio. This public client ID identifies Cursor; it is not a secret. The registered Cursor redirect has not been verified against every version. A redirect mismatch requires support; do not change account settings or guess a new client ID.

{
  "mcpServers": {
    "aixio": {
      "type": "http",
      "url": "https://data.aixio.app/functions/v1/platform-api-mcp",
      "auth": {
        "CLIENT_ID": "99521acb-7aa1-476d-9c56-c1936938b015"
      }
    }
  }
}

Other AI apps

Use the app’s remote MCP integration and the URL above. A browser tool alone cannot install an MCP connector. If OAuth registration or the callback is unsupported, report the exact error and client version to support@aixio.app. Do not use a REST key as an OAuth workaround.

2. Approve in Aixio

Your app opens Aixio’s sign-in and consent flow. Sign in with your existing account, review the requested access and approve. Return to your AI app. Your connection appears under Developers → Connected apps, where you can disconnect it.

The server advertises OAuth resource metadata through its unauthenticated 401 response and WWW-Authenticate header. A compatible MCP client follows discovery. Opening the MCP endpoint as a normal webpage can show an authentication error; do not paste passwords or tokens into chat or construct a manual token flow.

3. Verify without spending credits

List the connected Aixio tools and call balance. If list_workspaces is available, list my workspaces. Do not create or edit anything, send agent messages, run generators, or call design or design_status.

A successful tool listing and balance response confirm the connection, not that a paid generation will succeed. If your host has renamed tools with a prefix, use the discovered names.

Choose the right workflow

Troubleshooting