What Sunra MCP is
If you have a Sunra account and an agent you already work in, you have everything you need — there is no key to create and nothing to install by hand, which is the first thing people go looking for and don't find. MCP, the Model Context Protocol, is an open standard for letting an AI agent use outside tools; this page covers what Sunra's server gives yours, who pays for it, and when you want the API instead.
What your agent can do with it
Your agent sees a set of tools and picks the ones it needs. They fall into four groups:
| What you ask for | What the agent does |
|---|---|
| "Make me a poster" | Creates an image, video, audio or 3D job and waits for the result |
| "Which models can I use?" | Lists the catalogue and reads a model's schema before it sets any parameters |
| "What's this going to cost?" | Reads your balance and gets an estimate for the job it has planned |
| "Put it in my project" | Creates or picks a project and files the results there |
Because the agent can read each model's own schema, you don't have to know parameter names — you describe what you want and it fills them in. It can also take your own files as input (an image to animate, a reference photo, a voice sample) and hand back a link to everything it makes.
Creative tasks and production automation
Creative MCP and CLI support a task you start in a creative session with a defined scope and end condition. Your assistant may run scripts, complete multiple steps and generate multiple outputs. You do not need to stay present; spending follows your authorisation and confirmation settings.
Unless Sunra agrees otherwise in writing, use the Sunra API for independent production programs that repeatedly accept data or generation requests, scheduled or business-event-triggered workflows, and integrations into your own apps, websites, bots, platforms or software services. This applies to personal and internal use too. Starting each run manually, or routing it through an agent, MCP or CLI, does not change that requirement.
| Example | Which access to use |
|---|---|
| Ask your agent to make an ad for each product in a specified list, then stop | Creative MCP or CLI |
| Deploy a program that repeatedly takes product lists, even if you manually start each run | Sunra API |
| Schedule your agent to generate every day, or generate when a new order arrives | Sunra API |
| Run production workflows through MCP using a Sunra API key and API billing | API-key MCP, under the API rules |
You may still use outputs commercially and deliver them to clients under the Terms. The boundary concerns how you use the service, not the volume of your commercial distribution. Account sharing, website automation and bypassing limits or safety controls remain restricted.
Which apps can connect
Two kinds of client, set up two different ways:
- Agent apps — Claude Code, Codex, Cursor, Antigravity and Grok Bot. These get one setup prompt you paste into the agent; it installs the Sunra CLI and signs in for you.
- Chat apps — Claude and ChatGPT. These add Sunra as a connector in their own settings.
Any other MCP client that supports remote servers with OAuth sign-in can connect too: point it at the Sunra server URL and sign in. The URL, the setup prompt and each app's steps are all on the Sunra MCP page, and inside the product under MCP → Connect.
Connect your agent walks through every client step by step.
You don't need an API key
Sunra MCP signs in with your Sunra account, not with a key. You point the client at one URL, it sends you to Sunra in your browser, and you sign in and click Allow. Nothing to paste, nothing to store, nothing to leak.
Every app you allow is listed under Connected apps on the Connect page, with when it last used your account. You can disconnect any of them there, and it loses access immediately.
How it is paid for
Sunra MCP spends the same credits as the web app, from the same account — connecting an agent doesn't create a second balance or a second bill. Everything in Credits and plans applies unchanged: your allowance, your plan, refunds on failed renders.
If you belong to a team, your agent can ask which balance should pay and work against your personal credits or a team's. It never switches payer on its own.
Where your results go
Into a project in your Sunra account. The agent gets a link to each result as it finishes, and the project is a normal Sunra project afterwards — open it in the app to see everything the agent made, keep working on it, or download it. See Projects and assets.
That is the part that makes MCP more than a convenience: work that starts in your agent doesn't stay trapped there.
How MCP differs from the Sunra API
This comparison covers Creative MCP, which signs in with your account and spends credits. The separate API-key MCP server uses API authentication and billing; the Creative production-automation restrictions do not apply to it.
| Sunra MCP | Sunra API | |
|---|---|---|
| Use | A creative task you initiate with a defined scope and end condition | Independent production jobs, scheduled workflows and software integrations |
| How it signs in | Your Sunra account, in the browser | An API key |
| What it spends | Your Sunra credits | A prepaid US dollar balance |
| What you get back | Results filed into a Sunra project | A link to the result in the response |
Use Creative MCP for the creative tasks described above, and the API for production automation and software integrations, including internal tools. An account can use both.
Your prompts and files stay yours
Sunra doesn't use your prompts, uploads or generated content to train its own models, whether you work in the web app or through MCP.