YOUR AI. YOUR SCENE. CONNECTED.
From a conversation
to a scene you can direct.
Connect your AI assistant to Reelpen through MCP, the standard that lets AI applications use tools. Ask it to arrange a scene, direct a character, frame a camera or organize a film board. Keep refining the result in Reelpen.
Free Reelpen beta · Google sign-in · No Reelpen API key for the standard connection
01 / CONNECT YOUR AI APPLICATION
One address. Choose your assistant.
You need a Reelpen account and an AI application that supports remote MCP with OAuth sign-in. Use a desktop browser for the scene editor. Your AI application's own access rules and charges still apply.
https://beta.reelpen.ai/mcp
Paste this into the connector's server URL field. Opening it as a normal web page is not a connection test.
Claude
Web and desktop · custom connector
- Open Customize → Connectors, then + → Add custom connector.
- Name it Reelpen, paste the server address and select Add.
- Select Connect. In Reelpen, sign in with Google, review the requested permissions and choose Allow.
- Enable Reelpen from the conversation's + → Connectors menu.
In a managed workspace, an owner may need to add the connector first. Claude's setup instructions ↗
Codex
Desktop · remote MCP server
- Open Settings → MCP servers → Add server.
- Name it reelpen, choose Streamable HTTP and paste the server address.
- Save, then use Restart if shown. Select Authenticate when sign-in is required.
- Sign in to Reelpen with Google, review the permissions and choose Allow. Use /mcp to check the server.
Labels can vary by client version. OpenAI's MCP instructions ↗ · CLI setup below
02 / CHOOSE THE SCENE
Open your project. Allow this tab.
- Open your Reelpen workspace using the same Google account you used to authorize the connection.
- Open the project you want to work on. In the editor bar, select AI: allow in this tab.
- Keep the editor open and check the target project in Connected apps.
Connecting the account and allowing an editor tab are separate steps. Allowing another tab moves the live scene target there. Saved project and film-board permissions work separately, as described below.
03 / CHECK, THEN CREATE
Start with a read-only check.
Send this to your AI assistant. It should report the selected project and what's in the scene without changing anything.
Use Reelpen to read my allowed scene. Tell me the project name, the objects and cameras you can see, and whether the scene is live. Do not change anything.
You're ready when: the AI's project name matches the open editor, it reports a live scene, and its object list matches what you see. If it reports an old scene, use the troubleshooting steps before asking for edits.
Then give it a small, concrete shot.
In my allowed Reelpen scene, keep existing objects. Add one Dolly character with a short walking route and a camera that follows it. Read the current capabilities first, make the change as one batch, then show me a camera preview.
Watch the result in Reelpen and play the full movement before exporting. A scene-edit batch is one Undo step. Wait for Saved before closing the project.
BEYOND A CHAT RESPONSE
A connection to your filmmaking workspace.
Build the scene
Place catalog objects, extend roads, arrange props, change supported object settings and work with groups.
Direct the action
Set routes, pauses and gaze. Sequence walking, turns, sitting, standing and supported gestures. Preview the motion.
Frame the camera
Set framing, routes and camera movement. Adjust aspect ratio and resolution, then inspect a frame or a short preview clip.
Develop the film board
Organize shots, notes and references; link scenes and cameras. Requires film-board permissions.
Manage projects
List, name, duplicate and organize saved projects and reference images. Create new scenes with the relevant permissions.
Prepare your reference
Use supported image and GLB imports, inspect scene measurements, and prepare video, PNG or ZIP outputs in the editor.
The AI should read Reelpen's current capabilities before acting. File size, format, browser recording support and connection permissions determine what is available. Builder features are still evolving; this is not a promise that every Builder control is exposed.
Reelpen creates the editable scene and its references. Final AI video generation happens in the service you choose. Choose the right reference output →
YOU CHOOSE THE ACCESS
Know what you're allowing.
The permission screen lists what the application requests. A connection may include several of these permissions; only the granted ones apply.
| Access | What it allows | Needs an allowed editor tab? |
|---|---|---|
| Scene read / edit | Read the selected scene; apply edits and use live previews. Scene editing requires edit permission. Each edit batch is one Undo step. | Yes for live work. |
| Project read / manage | Read owned project names, version metadata and PNG references, including notes. Management adds rename, duplicate, trash, recover, version restore and reference changes. | No. These are saved account operations. |
| Film-board read / edit | Read saved boards, notes and references. Edit permission adds board and shot changes, trash and recovery. Scene and camera names can be used for linking. | No. This does not grant scene editing. |
| Create scenes | Create named projects using your account allowance. A new project does not automatically become the live target. | No for creation. Open and allow it to edit live. |
Pause live scene access
Choose Stop in the editor. This closes the live target. It does not revoke account access to saved projects or film boards.
Revoke the connection
Open Account → Connected apps and select Remove. The connection's tokens stop working and its row remains marked revoked.
Undo applies to editor history; it is not a universal rollback for saved project or film-board operations. Use their own recovery controls where available.
Your AI application receives a revocable Reelpen authorization, not your Google password. Data returned by tools is made available to that application and is subject to its data policies. Review the app name and requested permissions before allowing access.
Connected, but something isn't working?
The AI can't see my scene / NO_LIVE_SESSION
Sign in to Reelpen with the account used during authorization. Open the project, press AI: allow in this tab, keep the tab open and repeat the read-only prompt. A connector can be authenticated while no scene is live.
It sees the wrong project / TARGET_CHANGED
The most recently allowed tab is the live target. Return to the intended project and allow it there. Ask the AI to read the scene again before editing; it must not replay an old edit against a newly selected target.
Tools or film-board actions are missing
Enable Reelpen in the AI conversation and refresh or restart the connector. Check the permissions shown in Connected apps. An older grant may lack project or film-board access; reconnect and review the updated permission screen. A refresh alone does not grant new permissions.
Sign-in expired, was denied or used the wrong account
Start Connect or Authenticate again from your AI application. Finish the new sign-in and permission flow in the browser that opened it, with the intended Reelpen account. Do not reuse an old consent link. In a managed AI workspace, ask its owner whether custom connectors are enabled.
The editor and connector disagree after an update
Save your work, reload the editor, then allow the tab again. Refresh the connector's tool list or restart the AI application. Ask for a fresh scene read and capability check before continuing.
An edit timed out or the result is uncertain
Ask the AI to check the operation's status and read the scene before retrying. A timeout does not prove that an edit failed; sending it again as a new change can duplicate work.
The address or Copy button doesn't work
Use the full HTTPS server address ending in /mcp. If clipboard access is blocked, select and copy the visible text. Claude's remote connector runs from its cloud, so a localhost address on your computer will not work for it.
Advanced setup
Codex CLI or config.toml
With Codex CLI installed, add the remote server and complete OAuth sign-in:
codex mcp add reelpen --url https://beta.reelpen.ai/mcp codex mcp login reelpen
Alternatively, add this entry to ~/.codex/config.toml, then run codex mcp login reelpen:
[mcp_servers.reelpen] url = "https://beta.reelpen.ai/mcp"
Use codex mcp list or /mcp to inspect the connection. Configuration is shared by supported local Codex clients on the same host. Hosted web clients do not read this file.
Another MCP client
Use Streamable HTTP with the server address above. The client must support Reelpen's OAuth discovery, authorization and client registration flow. Compatibility depends on the client; configuring a URL alone does not establish permission. Check its documentation, complete sign-in and use the read-only prompt to verify the target.
A key for one project and the stdio bridge
The optional developer path is under Connected apps → Advanced → Project connections. A project key stays bound to its selected project; it does not receive account-wide film-board or project-management permissions.
With a local Reelpen checkout and Node.js 24 or newer, run node /absolute/path/to/reelpen/codex-ux/product/remote-mcp.mjs as your client's stdio server. Set REELPEN_REMOTE_URL to https://beta.reelpen.ai (the origin, without /mcp) and REELPEN_REMOTE_TOKEN to the project key through your client's secret/environment settings.
This is a network bridge, not offline access. Live edits still require an allowed editor tab. Keep the key out of chats and shared configuration; revoke it from Project connections when finished.
Updated 27 September 2026. Setup guidance checked against the linked official client documentation and Reelpen's current permission model. Client menus and availability can change.
Ready to direct your first shot?
Open a project, allow the tab and start with the read-only check.