How do I connect Claude to Valmera?

Use Valmera’s remote MCP URL in Claude’s custom-connector flow, authorize an eligible Valmera account, enable the connector in the conversation, then request your project list. In Claude Code, add the HTTP server and complete OAuth from the /mcp panel. A project-list response verifies that read operation; it does not prove that every editing tool or export is available.

Do I need a paid Valmera plan?

MCP access is included automatically for every verified Valmera subscriber on Pro or Frontier. Account creation and uploads are free, and your Claude plan and Valmera plan are separate.

Why can I sign in to Studio but not authorize the connector?

Studio and connector authorization can have different requirements. A Google-only account may need a Valmera password for the connector’s consent form. MCP access is now included for every verified Pro or Frontier subscriber. If an earlier attempt showed an account-not-enabled message, reconnect using the email on your active Valmera Pro or Frontier subscription.

Can Claude upload a video from my computer?

The client needs a way to read and transfer the file. Valmera’s upload_start returns a storage destination; the file bytes must actually be sent there before upload_finish is called. If your client cannot perform that transfer, upload in Studio and select the resulting project through MCP. Attaching a video to an assistant conversation is not by itself proof that Valmera received it.

Can Claude download the finished video?

The connector can return review media and temporary download URLs. The download_url tool can also retrieve an existing final, but cannot create it. Start the final export in Studio, wait for it to finish and inspect the complete MP4. What the client can download or show depends on that client’s media support.

Should I retry when a render call times out?

Inspect the returned job or project state first. If the service returned a job ID, use wait_for_job for that same operation. An observation timeout is not proof that the render failed. Start replacement work only after its actual state and any existing result establish what needs to happen.

Will these instructions work in every Claude workspace?

Client features and organization policies can affect connector setup. The instructions were checked against Anthropic’s current documentation on September 6, 2026; this review did not run a fresh end-to-end authorization test in every Claude client or workspace. Use the linked official guidance and your client’s current connection status.

Where can I see what Valmera actually produced?

The linked trim-and-reframe example provides its original silent source, exact source ranges, actual square Studio export and evidence record. It demonstrates a 12-second content edit with a measured five-second ending and an overlaid Valmera mark. It is one observed editing session, not a speech-accuracy or client-compatibility benchmark.

How to connect Claude to video editing

Connect an eligible Valmera account to Claude through the remote MCP endpoint below. Claude can then inspect your project and request supported edits; Valmera performs the media operations. Review the actual preview and create the final MP4 in Studio.

This guide covers the Claude app, Claude Code, source upload, a first editing request and common connection failures. Setup instructions and public discovery endpoints were checked on September 6, 2026.

Use this remote MCP URL

https://entrepreneur-bot-backend.onrender.com/mcp

This is the connector endpoint. Your Studio remains at valmera.io/studio.

Before connecting

Every verified Valmera subscriber on Pro or Frontier can connect through MCP automatically. Use the email on your active Pro or Frontier subscription. Account creation and uploads remain free.

If your account uses Google sign-in and you have never set a Valmera password, the connector’s email-and-password consent form may require you to set one through the site’s password-reset flow. If an old authorization attempt showed an account-not-enabled message, reconnect with your active Pro or Frontier account.

Anthropic currently lists remote custom connectors across Free, Pro, Max, Team and Enterprise, with one custom connector on Free. Organization owners configure managed connectors before members connect. Client entitlements are separate from Valmera access. See the official custom-connector guide.

Connect Valmera in the Claude app

1
Add the remote connector
Open Customize → Connectors. On an individual account, choose + → Add custom connector and enter the Valmera MCP URL above. In a managed workspace, use the connector configured by your organization owner.
2
Authorize the Valmera account
Choose Connect, complete the Valmera sign-in and review the requested access before pressing Allow. The server advertises dynamic client registration; this standard flow does not require you to invent a client ID or secret.
3
Enable it for this conversation
Use the conversation’s + menu and Connectors controls to enable the configured connector.
4
Confirm a read operation
Ask: List my Valmera projects and their IDs. Make no changes. Check the returned result and choose the intended project. A successful project listing verifies that read operation, not every later edit.

Menu labels and organization controls can change. The steps are source-checked instructions, not a promise of a fixed setup time.

The current menu paths are documented in Anthropic’s connector setup instructions.

Connect Claude Code with OAuth

Add the HTTP server in the intended Claude Code scope, then use the interactive MCP panel to authorize it:

claude mcp add --transport http valmera https://entrepreneur-bot-backend.onrender.com/mcp

# Inside an interactive Claude Code session:
/mcp

Select Valmera in the MCP panel and complete the browser sign-in. If the server is already configured, inspect it there instead of adding a duplicate. Check the connection status and request your project list after authorization.

This follows the official Claude Code MCP and OAuth instructions. The example configures the server; it does not install Valmera locally or transfer a video.

Get your footage into the selected project

A main source must meet both the current 14 GB and three-hour limits. Check supported formats and upload guidance for the full conditions. Successful decoding also depends on the file.

Route	What happens	Confirm before editing
Upload in Studio	Upload the source in Studio, then ask the connector to list and inspect your project	The selected project ID and completed analysis
Upload from a capable MCP client	Call upload_start, transfer bytes to its returned destination, then call upload_finish	Actual byte-transfer success, accepted completion and index_status
Use an accessible media URL	Use the current URL-ingestion tool only when the service can retrieve the media	The resulting project asset and analysis state; a pasted URL alone is not a successful import

There is no universal 64 MB rule for this workflow. The tool arguments carry metadata and upload instructions; the video bytes use the returned storage protocol. Client file access, transfer support, source limits and URL accessibility are separate constraints.

Make one edit you can check

For the downloadable original example source, a useful brief is:

Use the project ID I selected. Read its current edit. Keep source seconds 3–7, 12–16 and 19–23, in that order. Make a centered 1:1 crop and leave it silent. Render the current preview and report the project, version and output duration.

The recorded example used separate MCP calls for the cuts and crop. It produced a 12-second preview. Studio then exported a 17-second file including a five-second end card and a small overlaid Valmera mark. The example page shows the actual files and limits of that observation.

For your own footage, choose ranges from the actual source evidence. Check caption wording, important visual content and audio where relevant. Changes to timing can move later material; inspect the updated program before describing another correction.

Review the result and export in Studio

Confirm the project and edit version in the response. If rendering returns a job ID, follow it until it resolves. Inspect the actual preview your client can display or retrieve. A returned URL or a reassuring paragraph is not proof of visual review.

When the edit is ready, open that project in Studio and choose Export MP4. MCP cannot create the final export. It can retrieve a final that already exists. Check the downloaded file’s resolution, full runtime, sound, content and branding against your requirements.

If something goes wrong

The custom-connector option is absent: Check your client’s current feature availability and organization policy. In managed Team or Enterprise workspaces, the organization owner configures the connector before members connect.
The endpoint opens as an error in a normal browser tab: An MCP endpoint is a protocol endpoint, not a Studio webpage. Enter it in the client’s remote MCP configuration. Use the public server card for readable discovery information.
The consent form reports a password problem: For a Google-only Valmera account, use the site’s password-reset flow if you have not set a password. Also check the exact email and verification state; follow the displayed message.
Connecting apps is not enabled for this account: MCP is included with an active Valmera Pro or Frontier subscription. Reconnect using your verified subscriber email; contact support if the message persists.
The project list works but editing is refused: Read the editing error. Check project ownership, current entitlement or credit balance, indexing readiness and whether another operation is active. A successful read call does not establish write access.
The tool expects a project_id: Copy the immutable ID from the returned project record and pass it explicitly. Confirm the result names the intended project; do not rely only on an open-project pointer.
A tool is missing or rejects an argument: Refresh or inspect the client’s current tool discovery and use the advertised schema. Public catalogs and saved examples can differ from the authenticated session; optional services can also be unavailable.
An upload was accepted but the source is not ready: Confirm the byte transfer and upload_finish response, then check index_status. File receipt, completed analysis and an editable transcript are separate states.
A render says STILL RUNNING: Keep the job ID and inspect it with wait_for_job. If observation expires, check that same job or project state before starting duplicate work.
A preview link appears but no video is shown: Use the actual file or download surface supported by your client. Check its version and expiration. A text description or returned URL alone is not visual review.
Studio and MCP disagree about the current edit: Finish or resolve active work, then inspect the project and edit version again. Open the version you intend to continue and check whether the preview is current.

For Claude’s account-brokered remote connectors, Anthropic says the connection originates from its cloud infrastructure. An endpoint working in your browser does not prove that Claude can reach it. See its network requirements; local MCP servers are a different mechanism.

What was checked for this guide

Valmera’s public server card, OAuth discovery and protected-resource metadata were readable. The connected editing session’s advertised tools were compared with the public catalog. Those lists differed, so this guide directs actual calls to the current session schema.

The linked sample supplies evidence of one real MCP edit and Studio export. This documentation review did not perform a fresh Claude app or Claude Code authorization test, test every available tool, inspect the production account allowlist or establish access for every user. A readable public discovery document does not prove those outcomes.

Frequently Asked Questions

Inspect the editing result

Compare the original sample with Valmera’s actual output before choosing a larger workflow.

Watch the example →

See pricing →