ChatGPT Video Editing with MCP: Access, Setup & Uploads
Connect an eligible Valmera account to ChatGPT, then use the available tools to edit footage in a named project. Review the timeline and rendered preview before creating the final MP4 in Studio. ChatGPT access and Valmera MCP eligibility are separate requirements.
Setup guidance reviewed September 6, 2026 (UTC). The endpoint observations below retain their September 5 dates. This revision did not perform a fresh authenticated ChatGPT editing run. The source-to-export example shows a measured Valmera MCP edit and Studio export; it is not a ChatGPT client certification.
Public MCP endpoint: https://entrepreneur-bot-backend.onrender.com/mcp
Confirm Access Before Connecting
MCP access is included with active Pro and Frontier subscriptions. Creator does not include MCP access. Its authorization flow can recognize your credentials and still return Connecting apps to Valmera is not enabled for this account yet. If that happens on an active Pro or Frontier account, reconnect with your verified subscriber email and contact support if the issue persists. A paid ChatGPT plan, a readable public server card or free Valmera account creation does not resolve this access condition.
Use the account that owns the footage, and keep a note of the intended project ID. Once authorization succeeds, inspect that project before making changes. Studio remains a separate way to edit when the connector is unavailable; its own access and credit requirements still apply.
Choose the Connection Path You Actually Have
| Surface | Connection path | What to establish |
|---|---|---|
| ChatGPT web with an installed plugin | Use the plugin's supplied remote tools | The required plugin and tools are available to this account; this page does not establish a published Valmera plugin |
| ChatGPT developer mode | Add and test an MCP endpoint | Developer-mode access, successful discovery, authorization and the required operation |
| A local Codex client | Configure a direct MCP server connection | Supported transport/authentication and the tools actually available in that local session |
OpenAI's MCP guide distinguishes web plugin tools from direct local connections. Web chats do not read local Codex configuration. In the documented desktop path, use Settings → MCP servers → Add server, select Streamable HTTP, enter the URL, save and restart, then authenticate if requested. Hosted tools can have different capabilities.
MCP tools can read data or take actions. The model chooses a tool, while the server validates and performs the operation. A tool name in a directory does not establish account access, a successful write or acceptable video output.
Test the ChatGPT Developer-Mode Connection
- 1Confirm Valmera MCP accessUse a verified Valmera account with an active Pro or Frontier subscription. MCP access is included automatically for Pro and Frontier subscribers; your ChatGPT subscription is separate.
- 2Check developer-mode accessIn ChatGPT Settings, open Security and login and enable Developer mode if available. Account and workspace policy can affect access.
- 3Add the public endpointOpen ChatGPT Plugins, select the plus button and name the connection. Under Connection, enter Valmera's HTTPS MCP URL, including /mcp, then create it.
- 4Complete authorization and inspect discoveryFollow the Valmera sign-in flow and review the requested access. Inspect the tools the connection actually discovers; a public catalog is not an authenticated tool list.
- 5Attach the connection to a new conversationSelect the MCP connection in the conversation's tools menu. Begin by asking for available projects, with no editing or rendering.
- 6Select and inspect your test projectIdentify a project containing footage you can use for a test. Confirm its ID, current version, source and indexing state before asking for a change.
- 7Test one change and review the resultRequest one bounded edit on that test project. Track any returned job to its terminal state and inspect the new preview. Record what actually worked; use Studio for final delivery.
Use the current account controls and official OpenAI procedure. A small representative test establishes more than an endpoint URL alone.
The setup controls above follow the official connection and testing guide. Recheck that page if labels or access change.
Refresh Tools After a Server Update
For a developer-mode connection, open its page in ChatGPT Plugins and select Refresh. Inspect the discovered tools, start a new conversation and repeat the read-only project check. A conversation created before the update may not reflect the current connection metadata.
Published plugins can use reviewed metadata snapshots and have a separate update process. Refreshing a connection does not grant Valmera account access, add missing file-transfer capabilities or make a failed edit succeed. Use the exact tool schemas returned in the current session.
What the Public Endpoint Check Establishes
| Observed on September 5, 2026 | What it establishes | What remains unverified |
|---|---|---|
| GET /mcp returned 401 with a Bearer challenge | The unauthenticated request is challenged | A completed sign-in and authorized tool call |
| Protected resource and authorization metadata returned 200 | The MCP resource, valmera.edit scope, registration endpoint and S256 PKCE are advertised | The complete client registration, authorization and token-exchange flow |
| Public server card returned 200 and listed 134 tools | A dated inventory: 122 editing/review tools and 12 session tools | The authenticated tool list and the success of any particular operation |
| Upload limits returned 200 | Main video is limited by both 14 GB and 10,800 seconds | Whether a particular file uploads, indexes and exports successfully |
OpenAI's authorization documentation explains protected-resource discovery and supported client identification methods. Valmera advertises dynamic registration and S256 PKCE; metadata availability is not proof that all steps have completed. This guide makes no untested claim about token lifetime, credential storage or an authenticated streaming response.
Get Footage into the Valmera Project
Studio upload: upload your footage in Valmera Studio, then have the assistant list projects and open the intended project by ID. Confirm the input and indexing state. This avoids assuming that a file attached to a chat has also reached the editing service.
A supported import link: the catalog includes fetch_url. Use an accessible source you are permitted to import. A page URL may require login or fail to provide retrievable media; inspect the import result and project assets before requesting edits.
A client with file-transfer tools: upload_start and upload_finish support the separate upload flow. The client must be able to transfer file bytes using the returned instructions. This capability depends on the session, not simply whether its name is ChatGPT, Claude or Codex.
The checked upload response allows MP4, MOV, MKV, WebM and M4V main video within both limits. Read the upload guide for the workflow. A small test that uploads successfully does not establish performance for every long recording.
A Small Check with Observable Results
These are suggested prompts, not completed test results. Use footage you can edit and retain the project ID, version and returned identifiers. Adapt the request to the schemas actually discovered in that session.
| Stage | Suggested request | Evidence to inspect |
|---|---|---|
| Read | List my projects only. Do not create, edit or render anything. | A tool result with the expected project IDs, or a specific access error |
| Inspect | Open project [ID] and report its current version, source and indexing state. Do not alter the timeline. | The intended project and media, with a usable index for the next operation |
| Change | On this test project, remove only the agreed pause. Preserve the surrounding sentence and report the new version. | A new edit state with the intended range changed, rather than a confident chat claim |
| Review | Render a preview of that version, follow its job and review both sides of the cut. | A terminal job result and an inspected preview for that version |
The current catalog includes list_projects, open_project, project_state, get_edl, render_preview, wait_for_job and watch_video. Their presence does not guarantee that the current client can perform every review step. A queued job is pending; a completed render still needs content review.
Keep source timestamps separate from the preview clock. The measured trim-and-reframe example includes the original 25-second silent source, three retained four-second ranges and the downloaded 17-second final: 12 seconds of selected content followed by a five-second Valmera ending. A small Valmera mark also appears during the content. The source already contained its text and animation; the demonstrated operations are cuts and a centered square crop.
That example was produced through Valmera MCP tools and Studio, not a newly tested ChatGPT authorization flow. For an illustrative correction request, see the worked edit with source-to-output timing. Preserve approved selections and check the resulting version after restoring a cut.
Editing Access Does Not Include Every Delivery Operation
Under the checked public server card, MCP cannot initiate final export or delegate the edit to Valmera's in-house agent. SRT/VTT import/export, team seats and direct social publishing are also excluded. An available preview download is a review artifact.
Finish the accepted version in Studio, download the final MP4 and inspect the complete file, including the branded ending and runtime. It is re-encoded video, not an identical-quality guarantee. The export guide covers version selection, source readiness, subtitle-file limits and failed downloads.
Account creation and upload are free; indexing and agent editing require paid access. Consult current Valmera plans and the account's actual usage. The external assistant's own subscription or usage charges are separate.
Find the Stage That Failed
| Failure stage | Next check |
|---|---|
| Developer mode or plugin unavailable | Account controls and workspace policy; the server URL cannot grant client access |
| No tools discovered | Exact endpoint, transport, initialization, schemas and the connection's reported error |
| Sign-in does not finish | The displayed authorization error and current account; public metadata alone does not prove token exchange |
| Connecting apps is not enabled | Valmera account eligibility; valid credentials and the assistant's plan do not grant MCP access |
| Tools differ from the guide | Current session discovery; refresh a developer-mode connection after server metadata changes and start a new conversation |
| Wrong project or missing footage | Project ID, source assets and indexing state before any editing request |
| A job remains pending | The same job's current state; an observation timeout is not a terminal failure |
| Unsupported final export or subtitles | Use the documented Studio delivery step or a separate subtitle workflow |
If a connection cannot be completed, use Studio with your written brief. Work from one editing surface at a time. Resolve the active job and inspect the current version before changing surfaces; do not rely on a universal automatic refusal to protect competing edits.
Sources and Revision Scope
Valmera publishes this guide about its own service. OpenAI setup guidance was reviewed on September 6, 2026 (UTC). Public endpoint observations retain their September 5 dates; the account-enablement condition comes from Valmera's authorization implementation, without inspecting production configuration or arbitrary accounts. The original-source example was produced on September 6. No new ChatGPT client certification, performance benchmark or plugin-directory listing is claimed.
Frequently Asked Questions
Edit and Review in Valmera Studio
Upload footage, give a specific editing brief and review the result. Account creation and uploads are free; editing requires a subscription.
Create an account →