Most AI tools for content creation work like this: you ask an AI to write the script, you copy it, open another tab, paste it into your video tool, configure the settings manually, click generate, and wait. Then repeat.
Brainrot Shorts MCP cuts that loop entirely. Once connected, your AI — Claude, Claude Code, Cursor, or any MCP-compatible client — can generate ideas, write the script, build the video project, choose voices and backgrounds, trigger the render, and hand you the download link. All inside a single conversation.
This guide walks through what MCP is, why it matters for content creators, how to connect Brainrot Shorts to Claude, Claude Code, Cursor, or ChatGPT, and the prompts that make it worth setting up.
What Is MCP (and Why Should You Care)
MCP stands for Model Context Protocol. It is an open standard that lets AI assistants connect to external tools — like apps, APIs, and services — and control them directly from within a conversation.
You do not need to understand the technical details to use it. What matters practically:
Before MCP: You talk to Claude, it gives you a script, you manually build the video in Brainrot Shorts.
After MCP: You describe what you want. Claude handles the script and builds the video for you. You confirm the render and get the MP4.
The AI stops being a text generator and starts being a creative assistant that can actually produce finished work. The distance between "I want to make a TikTok about this idea" and "here is your video file" collapses to a few messages.
What Brainrot Shorts MCP Can Do
Once connected, your AI assistant has access to 25 tools across two groups:
Project, script, and render tools:
- Browse your existing projects and render history
- Generate script ideas for any niche (returns 12 ideas with titles and hooks)
- Write full 3-variation scripts (educational, entertaining, provocative)
- Create a new video project with the right character, background, and caption style
- Apply the script to the project and structure it into scenes
- Trigger the render and return the download URL when it is ready
Overlay tools (Creator/Pro):
- List available stickers, fonts, and images
- Upload custom images into the overlay layer
- Add, update, and remove overlays on a rendered video
- Trigger a re-render with overlays baked in
The core loop from idea to finished video can be driven entirely by conversation.
Connecting Brainrot Shorts to Claude
Claude connects through its own browser sign-in. There is no key to copy: you approve access once and Claude keeps the login for you.
Step 1: Open Connectors
In the Claude desktop app or on claude.ai, open Settings → Connectors. In the desktop app it is under the Claude menu; on claude.ai it is under your profile.
Step 2: Add a custom connector
Click Add custom connector, name it BrainrotShorts, and paste the server URL:
https://www.brainrotshorts.com/api/mcp
Use the www endpoint. Always use
https://www.brainrotshorts.com/api/mcpwith thewwwprefix — not the bare domain.
Step 3: Connect and approve access
Press Connect. A Brainrot Shorts window opens; sign in if you need to, then hit Allow access. You need a Creator, Pro, or Growth plan for the connection to be approved.
Step 4: Confirm the connection
Start a new Claude conversation and ask it to list your Brainrot Shorts projects. If the connection is working, Claude lists them straight from your account.
From here, Claude has full access to your Brainrot Shorts account through the conversation. If you are using a Claude client that cannot open a sign-in window, use an API key instead, as described in the next section.
Connecting via Claude Code, Cursor, or Another MCP Client
Every other client uses an MCP API key from the Connect an AI assistant page in your dashboard (Creator, Pro, or Growth). The key goes in the x-api-key header, and the server URL is always https://www.brainrotshorts.com/api/mcp, with the www: some clients drop custom headers when a redirect changes the host.
Claude Code
One command in your terminal:
claude mcp add --transport http brainrotshorts https://www.brainrotshorts.com/api/mcp --header "x-api-key: brs_your_mcp_api_key"
Start claude and ask it to list your Brainrot Shorts projects. From there the same prompts work as in the Claude app, right next to your code.
Cursor
Add this to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):
{
"mcpServers": {
"brainrotshorts": {
"url": "https://www.brainrotshorts.com/api/mcp",
"headers": {
"x-api-key": "brs_your_mcp_api_key"
}
}
}
}
Cursor lists the server under Settings → MCP with a green dot once it connects.
Any other client
The same JSON block works for any client that speaks MCP over HTTP and lets you set headers, including agent frameworks such as OpenClaw and self-built automations. Point it at the URL, send the key in the header, and test with:
List my Brainrot Shorts projects.
Connecting via ChatGPT (using mcporter)
ChatGPT does not support HTTP-based MCP servers natively yet, but you can bridge it using a tool called mcporter.
The mcporter config for your mcp_config.json:
{
"mcpServers": {
"brainrotshorts": {
"command": "mcporter",
"args": [
"--server",
"https://www.brainrotshorts.com/api/mcp"
],
"env": {
"MCPORTER_HEADER_X_API_KEY": "brs_your_mcp_api_key"
}
}
}
}
Once mcporter is running and the config is loaded, ChatGPT can call Brainrot Shorts tools the same way Claude does.
Example Prompts to Try First
The best way to understand what MCP unlocks is to see it in action. Here are the prompts worth starting with.
Generate a Reddit Story Video From Scratch
Generate 10 short-form video ideas for a Reddit story channel focused on r/AITA content.
Once I pick one, write the full script with Peter Griffin as the narrator,
then create the project with Minecraft parkour background and hormozi-style captions,
and queue it for render.
Claude will call script_ideate, show you the ideas, wait for your selection, call script_generate, create the project with project_create, apply the script with project_apply_script, and start the render with render_start.
Build a Batch of Videos Around a Single Niche
I want 5 short-form videos for a finance tips TikTok account.
For each one: generate an idea, write the entertaining script variation,
create a project with Stewie Griffin voice and anime background,
apply the script, and start the render.
Give me the project IDs when done so I can check the renders.
Claude will run the full creation loop five times in sequence, returning a list of project IDs to track renders against.
Pick the Right Character for Your Content
List all available characters with their voice IDs.
I'm making a revenge story from r/ProRevenge —
which character would you recommend and why?
Then list available backgrounds and suggest the best fit for the tone.
Claude calls character_list and background_list, then reasons about the best combination based on your brief. This is especially useful when you are starting a new channel and have not settled on a format yet.
Check the Status of Recent Renders
List my last 5 projects and tell me which ones have completed renders with download URLs.
Claude calls project_list and render_latest_url for each project, then returns a clean summary of what is ready to download.
Add Overlays to a Finished Video
I have a project called "AITA Neighbor Parking Story".
Load it, add a sticker overlay in the top-right corner at the 3-second mark,
then re-render and give me the updated download URL.
Claude will use project_get to find the project, then the overlay tools to apply the sticker and trigger overlay_render.
Why This Changes the Production Workflow
The biggest shift MCP creates is not automation — it is staying in the creative context.
When you build videos manually, every video requires a context switch: open the app, configure settings, navigate panels, click generate, come back later for the download. Each switch costs focus and breaks the creative momentum.
With MCP, you stay in one conversation. You can go from "I want to make content about side hustles this week" to five render-ready videos without leaving Claude. The AI handles the mechanical steps while you handle the creative direction.
That is a real difference at scale. A creator who posts five videos per week saves an hour or more of production time per week by keeping the workflow in Claude instead of bouncing between apps.
What Brainrot Shorts MCP Does Not Do
A few things worth knowing before you start:
It does not upload to social platforms. The render output is an MP4 download link. Posting to TikTok, Instagram, or YouTube Shorts is still manual.
Renders require explicit approval. The render_start tool requires approved=true to actually queue the job. Claude will always ask before it triggers a render — no accidental video charges.
The API key is account-wide. Any project you own is accessible. Do not paste the key into shared or public chats. Rotate it immediately from the MCP Access dashboard if you think it has been exposed.
MCP access requires Creator or above. Free, Lite, and trial accounts cannot generate MCP API keys. The feature unlocks after upgrading.
Setting Up Your First Automated Content Run
Once the connection is working, here is the fastest way to get real value from it:
- Open Claude (or Claude Code, or Cursor) with Brainrot Shorts connected.
- Tell it your niche and the platform you are targeting.
- Ask for 10 to 15 video ideas in that niche.
- Review the ideas and pick the best three to five.
- For each selected idea, ask Claude to write the script and create the project.
- Review the scripts in the Brainrot Shorts dashboard if you want to make adjustments.
- Ask Claude to start the renders for all approved projects.
- Download and post.
A run like this, which would normally take 30 to 60 minutes of manual clicking and copying, can be done in one focused conversation in 10 to 15 minutes.
With a scheduled agent, you can go further: run this content creation loop every morning, generating and rendering a new batch of videos before you even open your laptop.
Which Client Should You Use?
Every client gives you the same Brainrot Shorts tools. The difference is where and how you interact with them:
| Client | Best for |
|---|---|
| Claude (claude.ai / Desktop) | Focused creative sessions, back-and-forth script editing, exploring ideas |
| Claude Code / Cursor | Creating videos next to your code, scripted batches, scheduled automations that run in the background |
| ChatGPT via mcporter | Teams or workflows already built around ChatGPT where switching to Claude is not an option |
For most solo creators starting out, Claude is the fastest path. For creators who want to automate their production pipeline, Claude Code or Cursor with an API key is worth the extra minute of setup.
Final Takeaway
MCP is the part of Brainrot Shorts that turns any AI assistant into a production partner. You bring the creative direction. The AI handles the mechanical steps: ideation, scripting, project setup, rendering.
Claude is the fastest to set up — five minutes and you are running. Claude Code and Cursor take one more step (a key) and open up scripted and scheduled workflows. Every client gets the same tools and the same finished MP4s at the end.
If you are on Creator, Pro, or Growth, open the dashboard, grab your MCP key, and follow the setup for whichever client fits your workflow. If you are not yet on a qualifying plan, the pricing page breaks down what is included on each tier.