Model Context Protocol

Your edit bay,
inside the chat.

Connect NimbleAI to Claude and check renders, browse your library, and kick off exports — without ever leaving the conversation.

nimbleai.mcp — session rec
00:00 You → Claude

"Turn my last upload into 3 vertical clips."

00:02 Claude → MCP

Calling list_videos() to find the source file.

00:05 NimbleAI

Rendering — subtitles, crop, viral scoring.

00:24 Claude → You

"Done. 3 clips ready, top score 87."

Get connected

Three steps. No API key.

NimbleAI MCP runs on your existing Claude account — Claude.ai, Claude Desktop, or Cowork. Support for other MCP clients isn't ready yet.

01

Copy the connector URL

This is the address Claude will call to reach your NimbleAI account.

https://nimbleai-edit.com/mcp
02

Add it in Claude

Go to Settings → Connectors → Add connector, paste the URL, and name it NimbleAI.

Open Claude Connectors →
03

Ask Claude to use it

Once it's connected, just ask — Claude calls the right tool for you.

Try it now →
The toolkit

Every tool on the timeline.

Two are live today. The rest are next up in the render queue — built the same way, shipped as they're ready.

list_videos() Live
Browse your library
Pull your recent uploads with AI title, viral score, and clip count — without opening the dashboard.
What are my last 5 uploads, sorted by viral score?
get_job_status(jobId) Live
Track a render
Ask where an export stands — downloading, burning subtitles, zipping — in plain language, in real time.
Is my export from this morning done yet?
upload_video(url) Soon
Start a render from chat
Drop a link or a file and kick off a render without ever opening the upload screen.
Turn this YouTube link into three 9:16 clips.
apply_subtitle_style(name) Soon
Swap styles by name
Ask for "Cinematic Bold" or "Gaming Neon" on your next export — no dropdown, no preview grid.
Re-render that clip with the Luxury style.
get_transcript(videoId) Soon
Pull a transcript
Grab the full Whisper transcript of any video to draft titles, hooks, or descriptions.
Write three hook ideas from my last podcast upload.
trigger_render(params) Soon
Custom exports on demand
Set crop, format, and trim points in one sentence, then let the pipeline take it from there.
Export that clip 1:1, trimmed to the first 30 seconds.
Compatibility

Works wherever Claude does.

NimbleAI MCP speaks the same protocol as every Claude surface — connect once, use it from any of them.

Claude Desktop
Claude Code
Claude.ai
NimbleAI
MCP
Claude Desktop
Claude Code
Claude.ai — Custom Connectors
FAQ

Before you connect.

Model Context Protocol is an open standard that lets Claude call tools on external services — like NimbleAI — directly inside a conversation, instead of you copying data back and forth.
No. Custom connectors work on Free, Pro, Max, Team, and Enterprise plans. Free accounts are limited to one custom connector at a time, so make sure NimbleAI is the one you add.
Tool calls run against your own NimbleAI account. Nothing is shared with other users, and video files never pass through Claude — only metadata like status and titles do.
It's next on the render queue. Live tools ship first, the rest follow as they clear testing — check back or watch the changelog.

Ready to let Claude
run the timeline?

Two tools are live. Connect NimbleAI MCP and start with those — the rest ship as they're ready.

Connect to Claude