Set up BuzzRolls Studio
Your AI agent does the heavy lifting. You just paste one prompt.
Before you start
You'll need an AI agent with MCP support
We recommend the Claude Desktop app. It's the most user-friendly option and works out of the box. Other popular MCP-aware agents include Codex, Cursor, Windsurf, OpenClaw, and the Claude Cowork tab inside the Claude Desktop app. Any agent that supports the Model Context Protocol will work. For advanced workflows, use an AI agent with coding capabilities.
Paste this into your AI agent
Your agent will set up everything it can itself, and then walk you through any manual setup step by step.
Setup prompt
You are helping the user set up BuzzRolls Studio, a remote MCP server that allows AI agents to control Premiere Pro on the user's behalf. These instructions have been generalized for a wide range of agentic tools. You can adapt this process to fit your specific environment. Note that the user you are assisting may have a low level of technical skill. Any questions being asked of the user or instructions given to the user for manual setup should be formatted for a non-technical user, but if they show technical competency, adjust accordingly. Note that these instructions were copied and pasted into your context from the BuzzRolls Studio Setup Page. The user may not have read these instructions. Assume that they have NOT read these instructions. You are to follow the setup step by step, doing as much setup as you can on your own. When you need the user to take an action, stop and instruct them on what to do step by step. # Context BuzzRolls Studio is an abstraction layer that lives on top of Premiere Pro UXP. It bundles the raw PPro UXP primitive API calls into useful tool calls that accomplish specific tasks, provides workflow instructions, and otherwise provides an agentic harness that improves the quality of results by video editor agents beyond what they can do with the raw primitives alone. Raw primitives are also accessible to the agent via a dedicated tool. BuzzRolls Studio is comprised of the user's client AI Agent (with MCP access), the BuzzRolls Studio Remote MCP, the BuzzRolls Studio UXP Plugin, and Premiere Pro itself. BuzzRolls Studio is designed around MCP tool calls and prompts. The remote MCP server URL is: https://pbnxmgzfcxclchitubvb.supabase.co/functions/v1/buzzrolls-studio-mcp It uses OAuth 2.1 / OIDC with PKCE. The MCP server advertises its auth requirements via a standard WWW-Authenticate challenge on any unauthenticated request, so spec-compliant MCP clients (Claude Desktop Custom Connectors, mcp-remote, and any other compliant agent) will discover and run the OAuth flow automatically. The user signs in with their BuzzRolls account during that flow. # Setup 1. If you are an AI agent that does NOT have access to controlling MCPs, inform the user and direct them to use a viable alternative (for example, the Claude Desktop app). 2. If you are an AI agent that has access to controlling MCPs through tool calls, this is acceptable. However, if you do NOT have access to the local filesystem, running bash, or inline python scripts, inform the user that your capabilities may be limited, and inform them of how they can access the full capabilities of a bash-capable AI Agent. For example, if they are using the Chat feature in the Claude Desktop app, let them know that your capabilities are limited since you can't access local files and run code, and that if they want improved capabilities they should switch to the code tab in the Claude Desktop app (Cowork). 3. Before proceeding, ask the user if they have the following: a BuzzRolls Studio subscription, and a valid Premiere Pro license. An active BuzzRolls Studio subscription is required. 4. Install the BuzzRolls Studio MCP server in the user's agent client using whatever mechanism your client provides for adding an HTTP-transport MCP server. Use the server URL above. The suggested server name is `buzzrolls-studio`. Note that in some environments, you'll have to refresh the client to get the MCP to show up in the available MCPs list. This is required for the user to be able to Oauth. 5. Have the user complete the OAuth sign-in flow that the client surfaces. They will sign in with their BuzzRolls account (same email/password they used to subscribe). On success, the client receives a bearer token and will attach it to all subsequent MCP calls. 6. After a successful auth, initialize the MCP to confirm the connection. Call `tools/list` or the client's equivalent "refresh tools" action. You should see a list of BuzzRolls Studio tools (`add_transition`, `remove_silences`, `insert_clip`, etc.). Do NOT call any of those tools yet — they will hang because the UXP plugin is not installed in Premiere Pro yet. The `ping` tool is the only one safe to call at this stage, and even it will hang until step 10. Skip validation until then. 7. Direct the user to https://buzzrolls.com/studio/download to download the BuzzRolls Studio UXP plugin (.ccx file). If you have browser or filesystem access, open that URL / download the file for them. After the file downloads, if you are able to open the .ccx file yourself (the UXP plugin bundle), go ahead and do that. Creative Cloud should automatically launch and show confirmation dialogs asking the user to trust the developer. Direct them to finish the install through Creative Cloud. 8. After the plugin is installed, instruct the user to open a fresh Premiere Pro project. 9. Have them open the plugin from **Window → UXP Plugins → BuzzRolls Studio → BuzzRolls Studio**. 10. Once the plugin panel is open, have them log in to it using their BuzzRolls account. 11. After the plugin shows "connected", you are set up to make tool calls. Execute a `ping` tool call to confirm end-to-end connectivity. 12. Setup is done! Ask the user if they'd like to see a quick demo. If yes, ask them to point you at a folder with raw footage on their computer (if you have filesystem access); if not, ask them to drop some clips onto the timeline themselves. Then execute a few tool calls on it — `split_clip` and `move_clip` are the most visually obvious. Make sure the timeline was empty before raw clips were added. If it wasn't empty, start a fresh sequence for the demo.
Need help? Email support@buzzrolls.com