Nodaro MCP

The Nodaro MCP server lets an AI assistant use Nodaro on your behalf. You connect Claude, ChatGPT, Cursor or another client that speaks the Model Context Protocol (MCP) and sign in with your Nodaro account. The assistant can then generate images, video, voice and music, build and run workflows, manage your characters and direct complete films from a conversation. Everything it makes is saved to your Nodaro library, and every workflow it builds opens in the editor.

The server URL

https://mcp.nodaro.ai/mcp

Every client uses this one URL. The server speaks MCP over the Streamable HTTP transport and signs you in with OAuth, so there is no API key to copy.

Two similar addresses do not work:

• https://api.nodaro.ai/mcp — this domain does not exist, so the connection fails before it reaches Nodaro.
• https://app.nodaro.ai/mcp — this is a web page about MCP, not the server.

Connect in about a minute

What an assistant can do

The server exposes about 200 tools. The assistant discovers them when it connects, so you ask in plain words and it chooses the tools.

Some tools exist only to teach the assistant how to work with Nodaro. start_workflow_editor, get_node_skill, start_film_director, start_video_director and get_recipe return instructions instead of media. They are free and change nothing in your account.

Sign-in and permissions

The server uses the OAuth 2.0 authorization code flow with PKCE. The first time you connect, your client registers itself with Nodaro and sends you to the consent screen.

• The consent screen shows the app, the Nodaro account it connects as, and the permissions it asks for. Click Use a different account to connect another account.
• The client name is not verified. A client that registered itself chose its own name, and the consent screen shows a warning about it. Approve only when the app is the one you are using.
• Access lasts 90 days. There are no refresh tokens, so after 90 days your client asks you to sign in again.
• You can revoke access at any time. Open app.nodaro.ai/settings/developer-apps and revoke the app in the list of apps you authorized.

Permissions (scopes)

Each tool needs one or more permissions. A tool whose permissions you did not grant is left out of the tool list entirely: it does not appear and then fail.

A few tools need no permission and are always visible, such as ping, list_models and the guide tools. The tools reference lists the permission of every tool.

The workspace permissions are not part of connections authorized before workspaces existed. To use the workspace tools, remove the connector and add it again.

What it costs

• Connecting is free. There is no separate plan for MCP.
• Generation tools spend credits from your Nodaro account, at the same prices as the editor and the API. Credits explains how prices work, and each model page lists its price.
• Discovery and guide tools are free, for example list_models, get_node_skill, list_shot_shapes and get_recipe.
• A failed generation is refunded. Credits reserved for a failed job come back automatically. The exception is a failure in post-processing after the model already delivered its result.
• Some tools quote before they spend. start_recast without confirm, plan_studio_export and the studio tools with dry_run: true return a price and start nothing.
• Retries are safe with a retry token. run_workflow, run_app, run_component and several production tools accept client_request_id. Send the same value again after a timeout, and Nodaro does not start or charge the run twice.

On Nodaro Cloud, check_balance returns your balance and credit_transactions lists your purchases.

Where your results go

• Your library. Every result is saved to your Nodaro library, exactly like a run from the editor.
• Job cards. In clients that display MCP Apps, such as Claude on the web, a generation shows a card with live progress and then the result. Other clients check the job with get_job or wait_for_job.
• The mcp project. Workflows the assistant creates live in a project named mcp, which Nodaro creates on first use. The dashboard lists them under MCP Workflows. The assistant can see the names of all your projects, but it edits and runs only the workflows in the mcp project.
• The run list. A run that an assistant started carries a via MCP badge, or the client's name when Nodaro knows it, such as via Claude.

The MCP page on nodaro.ai

nodaro.ai/mcp is the quick way to connect. It has a Connect to Claude button, a field that copies the server URL, and a tab with three short steps for each client. These docs add the full steps for each client, the reference of every tool, and guides for the directors and pipelines.

Nodaro Cloud and self-hosted installs

Nodaro Cloud runs the MCP server at mcp.nodaro.ai for every account.

Self-hosted Community and Business installs include the same server, turned off by default. The operator turns it on and gives it its own address; see MCP on a self-hosted install. Connect your client to that address instead of mcp.nodaro.ai.

Some tools exist only on Nodaro Cloud, for example the studio production and recast tools, create_explainer, plan_edit and the credit tools. On other installs these tools are absent or answer not_available.

Next steps