Design with an agent: OIM over MCP

A .oim file can be designed by hand in the editor, but it can also be asked for. OIM runs a Model Context Protocol server so an AI agent can create projects, compose layers and export signed files on your account, under the same rules as if you did it yourself.

This guide covers how to connect it, what a typical flow looks like, and what it cannot do.

Connect

Add https://mcp.oim.media/mcp as a custom connector in your client (Claude, for example). The first call asks you to sign in to OIM; the client stores the token and you are done. There is no API key to copy or keep.

The connector is in closed beta: it works on accounts with access to OIM-Studio.

A typical flow

Ask for something concrete: "a 1200×630 card announcing the offline viewer, in English and Spanish, with an animated headline". The agent chains calls like these:

1. oim_design_guide to read the design rules before starting.
2. oim_create_project and oim_set_canvas_size for the canvas.
3. oim_create_artistic_text with the text in both languages at once.
4. oim_set_animation for the headline's motion.
5. oim_preview to look at the result and fix it.
6. oim_export for the signed .oim.

Everything lands in your projects: you can open it in the editor and refine it by hand.

How it gets signed

The agent signs nothing. oim_export asks your open editor tab to export, and the tab uses the same signing service as a manual export. That is why the editor must stay open while the agent exports.

Security and limits

• The token is your session: the agent sees and touches only what your account can.
• Revoke the app and the next call fails.
• 60 requests per minute per account.
• Files up to 5 MB come back in the response; larger ones stay in your media.
• AI is paid by your agent's provider; OIM adds no charges.

The full reference, with every tool and error, is in the MCP documentation.