# Nodaro MCP

> Connect Claude, ChatGPT, Cursor or any MCP client to Nodaro to generate media, build and run workflows, manage characters and direct films from chat.

Source: https://nodaro.ai/docs/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

```text
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

### Copy the URL

Copy `https://mcp.nodaro.ai/mcp`.

### Add it to your client

Open the connector or MCP settings of your client and add a remote server with the URL. Claude, VS Code, Cursor and Goose also have a link that opens the dialog with the details filled in. [Connect a client](https://nodaro.ai/docs/mcp/connect) has the exact steps for each client.

### Sign in and allow access

Your browser opens the Nodaro sign-in page. Sign in, review the permissions on the consent screen, and click **Allow**.

### Ask for something

Ask the assistant, for example: "Generate an image of a knight with Nodaro." To test only the connection, ask it to call the `ping` tool. The tool answers with your Nodaro user id and the name of your client.

## 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.

| Goal | Main tools | Read more |
| --- | --- | --- |
| Create and edit images | `generate_image`, `modify_image`, `edit_image`, `image_overlay` | [Image tools](https://nodaro.ai/docs/mcp/tools/image) |
| Create video from text or a picture | `generate_video`, `animate_image`, `extend_video`, `lip_sync` | [Video tools](https://nodaro.ai/docs/mcp/tools/video) |
| Cut, caption and assemble video | `trim_video`, `combine_videos`, `add_captions`, `overlay_images` | [Video editing tools](https://nodaro.ai/docs/mcp/tools/video-editing) |
| Voice, sound effects and music | `generate_speech`, `generate_dialogue`, `text_to_audio`, `suno_generate` | [Audio tools](https://nodaro.ai/docs/mcp/tools/audio), [Music tools](https://nodaro.ai/docs/mcp/tools/music) |
| Build, edit and run workflows | `create_workflow`, `update_workflow_json`, `run_workflow` | [Project and workflow tools](https://nodaro.ai/docs/mcp/tools/projects-and-workflows) |
| Run your published apps and saved components | `run_app`, `run_component` | [App and component tools](https://nodaro.ai/docs/mcp/tools/apps-and-components) |
| Keep a character, place or prop consistent | `create_character`, `generate_location`, `generate_object`, `generate_creature` | [Character tools](https://nodaro.ai/docs/mcp/tools/characters) |
| Direct a film | `start_film_director`, the studio production tools, the recast tools | [Film Director](https://nodaro.ai/docs/mcp/film-director), [Studio productions](https://nodaro.ai/docs/mcp/studio-productions), [Recast](https://nodaro.ai/docs/mcp/recast) |
| Make a narrated motion-graphics video | `create_explainer`, `create_launch_video` | [Video Director](https://nodaro.ai/docs/mcp/video-director) |
| Build and render a 3D scene | `generate_3d_scene`, `edit_3d_scene`, `render_3d_scene` | [3D scenes](https://nodaro.ai/docs/mcp/3d-scenes) |
| Follow a tested multi-step playbook | `get_recipe` | [Content recipes](https://nodaro.ai/docs/mcp/recipes) |

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](https://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.

| Scope | What it allows |
| --- | --- |
| `workflows:read` | Read your projects, workflows, saved components and studio productions |
| `workflows:write` | Create, change, import and delete workflows in the mcp project, and create and edit productions |
| `workflows:execute` | Run workflows, apps and components, and use every generation tool |
| `jobs:read` | Read your jobs and runs, wait for a job, and diagnose a failure |
| `assets:read` | Browse your gallery, uploads and favorites, and read your characters, locations, objects and creatures |
| `assets:write` | Upload files, create and update characters and locations, approve images and mark favorites |
| `credits:read` | Read your credit balance and purchase history |
| `apps:read` | List published apps and read their inputs |
| `presets:read` | List and read node presets |
| `pipelines:read`, `pipelines:execute`, `pipelines:approve` | Read, run and approve Story to Video pipelines |
| `workspaces:read`, `workspaces:write` | List your workspaces and choose the one the session works in |

A few tools need no permission and are always visible, such as `ping`, `list_models` and the guide tools. The [tools reference](https://nodaro.ai/docs/mcp/tools) 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](https://nodaro.ai/docs/concepts/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](https://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](https://nodaro.ai/docs/self-hosting/mcp). 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

  - [Connect a client](https://nodaro.ai/docs/mcp/connect): Step-by-step setup for Claude, ChatGPT, VS Code, Cursor, Cline, Continue, Goose and your own client.
  - [Tools reference](https://nodaro.ai/docs/mcp/tools): Every tool, its parameters, its permission and its price.
  - [Film Director](https://nodaro.ai/docs/mcp/film-director): Describe a film and watch the assistant build it on your canvas.
  - [Troubleshooting](https://nodaro.ai/docs/mcp/troubleshooting): Fix sign-in errors, missing tools and failed jobs.

## Frequently asked questions

### What is the Nodaro MCP server URL?

The URL is https://mcp.nodaro.ai/mcp, and it is the same for every client. Clients connect over Streamable HTTP and sign in with OAuth, so you never paste an API key.

### Does using Nodaro through an AI assistant cost extra?

No. Connecting is free. Tools that generate media spend credits from your Nodaro account at the same prices as the editor, and discovery and guide tools cost nothing.

### Which AI assistants can connect to Nodaro?

Claude, ChatGPT in Developer mode, VS Code, Cursor, Cline, Continue, Goose and other clients that support remote MCP servers over Streamable HTTP with OAuth sign-in.

### Why does my assistant not see some Nodaro tools?

A tool whose permission you did not grant is left out of the tool list entirely, and some tools exist only on Nodaro Cloud. Remove the connector, add it again and allow every permission on the consent screen.

### Can I use MCP with a self-hosted Nodaro install?

Yes, when the operator turns the MCP server on for that instance. Your assistant then connects to the instance's own MCP address instead of mcp.nodaro.ai.