Connect an AI client with MCP

Nubu's MCP server lets an AI client such as Claude Code control Nubu without opening the interface: search the library, create campaigns and flows, build and edit Motion projects headless, preview a frame, queue renders and publish templates, all with your own permissions. It is part of every paid plan (Starter, Pro and Business+) and uses the same tools, guides and limits as the AI assistant inside Nubu.

Before you start#

• Your organisation's owner switches MCP on under Settings > Integrations > MCP and chooses who may connect (Members and above, Admins and above, or Owners only). Until then no one can connect an AI client to that organisation.
• You need a Nubu account that is a member of the organisation, at or above the role the owner chose.

1. Add Nubu to your client#

In Claude Code:

claude mcp add --transport http nubu https://mcp.nubu.app/mcp

Any MCP client that speaks Streamable HTTP with OAuth works the same way: the server address is https://mcp.nubu.app/mcp.

2. Authenticate#

Type /mcp in Claude Code, pick nubu and choose Authenticate. Your browser opens Nubu's sign-in. If you are already signed in to Nubu you go straight to the next step; otherwise sign in the usual way.

3. Approve the connection#

Nubu shows Connect Claude to Nubu: the app that is asking, a dropdown of the organisations you can connect (members of, MCP enabled, your role high enough), and the permissions the connection will have. Those permissions are your own Nubu permissions in that organisation, never more: an app connected through you cannot do anything you could not do yourself.

Choose the organisation and click Allow access to Nubu, or Cancel. One connection acts in one organisation; connect again to switch.

4. Work from your chat#

Back in your client, the connection is ready. Ask for what you want in plain words. Some examples:

• "List my campaigns and the flows in the autumn one."
• "Create a Motion project called Spring banner with a 1080 by 1080 comp and a headline layer."
• "Show me frame 24 of the hero comp." (the frame is rendered by the render farm and shown inline; it counts as a render)
• "Queue a render of the hero comp with MP4 H.264."
• "Publish this project as a template version."

Destructive actions (deleting, building, queueing renders, publishing) ask you to confirm first. Approving creatives and setting a flow's Auto Queue apply directly.

Revoking a connection#

Under Settings > Privacy & Security > Connected apps you see every app you connected, the organisation it acts in and when it was connected. Revoke stops its access at its next request; renders it already queued carry on. You can connect the app again at any time.

Good to know#

• A connection follows your membership: if you leave the organisation, or the owner switches MCP off or raises the required role, the next request is refused.
• Your organisation's AI budgets and the per-minute limit are shared between the assistant and MCP.
• Motion edits over MCP save one revision per change and respect the editor: a project open in someone's editor refuses edits until they close it.
• Frame previews are rendered by the farm and deleted as soon as they are shown; they count towards your plan like any render.
• Web searches are your AI client's own: Nubu's in-app assistant has a web search tool, the MCP does not offer it, so your client looks things up with its own search.
• Assets the AI puts into your library always land in a named folder with at least ten tags, and the compositions it creates are filed in the Project panel (templates under Templates, everything else under Precomps) with motion blur on; your own uploads and compositions are untouched by those rules.
• Finished files are one call away: get_render_download hands your AI client a download link that lives about an hour (or one ZIP export of several renders, or a ready export of yours); Nubu never writes those links into its logs or the conversation record. Publishing over MCP checks every dynamic field before writing and reads the template back afterwards: a field bound to a layer inside a precomp the master embeds publishes under the master, and a field no template comp reaches refuses the publish by name.