mcp

ixi runs an MCP server, so an AI assistant you already use can open your canvases, run your processes and read the results. You sign in with your own ixi account, there is no key to copy, and the assistant sees only what you can see.

connect claude

1. Open Organization settings → API keys, or the MCP developer page. Both show Connect with Claude.
2. Click it. It copies the server URL, https://api.ixi.so/mcp, and opens Claude's connector settings.
3. In Claude, click Add custom connector, paste the URL, name it ixi, and click Add.
4. Click Connect, sign in to ixi, and approve.

It works in Claude on the web and in Claude Desktop. On Team and Enterprise plans an Owner adds the connector once for the workspace, then each person connects with their own ixi login.

Not on Claude? Any client that speaks streamable HTTP with OAuth works. In Claude Code:

claude mcp add --transport http ixi https://api.ixi.so/mcp
claude mcp login ixi

Cursor and others point at the same URL. Full setup, with troubleshooting, is in the developer reference.

check it worked

Ask the assistant: "List my ixi orgs." It should answer with the orgs you belong to and your role in each. Every other request starts from there.

what you can do from claude

Ask for	What happens
browse	list and search canvases, read their nodes and files
build	add nodes, edit them, connect them, add files from a run
run	start a process, a pipeline or a model node, then read the results back
tables	query rows and fill a process column across rows (50 rows per call)
code	write and test sandbox apps and scripts
3D, video, design	read and edit model3d, cut and design nodes, and look at them with a still
report	file a support ticket for you

Changes appear live in any open browser tab. Tools that edit or delete are marked as such, and Claude asks before each call.

limits & good to know

• You can read any canvas shared with you, but only run processes in orgs you belong to. Running spends that org's credits; see billing and credits.
• At most 100 runs per person per 24 hours start over MCP, on top of the normal daily run limit.
• A run has no "finished" event: it's done when it's idle and has published results. Ask Claude to wait on it.
• If a run asks a question, it waits for a person in ixi. Claude can tell you it needs one.
• If no ixi tools show in a chat, disconnect and reconnect the connector or start a new chat.
• Sandboxes that use org secrets can be read and run but their code can't be edited over MCP.

related

• developer reference — every tool.
• secrets and API keys
• your product — embed processes in your own app instead.