Vidreno MCP Server

Add a credit (role + name) to a film's credit list, optionally linking it to a Vidreno filmmaker by username (they get a request to accept) or inviting the person by email (the invite is sent straight away; at most 60 credits per film, invites are rate-limited per day). Returns the full credit list with credit_ids.

Create a new draft film from a title, exactly as the Studio's add-film dialog does. The draft starts as Buy or rent with no prices, no poster and no files, and is not public until publish_film. Returns the film's id, editor link and publish checklist (the same shape as get_film), so the next steps are update_film (details, access: free or paid, prices), start_film_upload (main film), the poster in the film editor, then publish_film.

Full details of one film: status (draft/published), how it is released (free to watch or buy/rent) and its prices, play count, metadata, main film and trailer state, credits (with credit_ids), the publish checklist and its public page link. Films cannot be embedded.

The user's film orders (buy and rent), newest first, one row per order: film, purchase or rental, price before tax, the payment processor's fee (processor_fee_estimated is true until the real fee is known; it comes off the price first), Vidreno's 10% cut of what is left after that fee, paid or refunded, what was credited and what the order is worth in the balance today (net: 0 once refunded), and dates. Never includes who bought. Filter by film_id (public film id) or status; paginate with page/page_size. Read-only.

Remove one credit from a film's credit list by credit_id (from get_film). A pending invite for it stops working.

Change a film's metadata (title, synopsis, director and cast lines, year, runtime, genres from the fixed list, country of production, what it was shot on (capture_format, camera), student_film, filming_locations, awards (checked by the Vidreno team before they show publicly), IMDb link, extra links, the AI disclosure mostly_ai_generated shown as 'Made with AI' on the film page, allow_search_engines: off keeps the page reachable by link but hides it from search engines and the sitemap, show_view_count: off keeps the film's view count off its public page and the profile cards), how it is released (access: free = Free to watch, which needs no price; paid = Buy or rent) and its buy/rent prices in US cents (minimum $1.00), or detach its trailer. Only the fields given are changed; the same validation as the film editor applies, and a published film whose publish checklist no longer passes returns to draft. The poster cannot be set here: it is added in the film editor (the edit link). The main film is replaced with start_film_upload, never detached.

Change one credit in place by credit_id: its role or name, or who it is linked to (a Vidreno username, which they are asked to accept, or an invite email, which is sent straight away; null clears). The credit keeps its id, position and, when only the role or name changes, its accepted or linked state. Returns the full credit list.

Add a role the project is looking for (the Studio's Roles tab): the role name, how many people, what it involves and the pay (paid with an amount, currency and per day / flat / per hour; expenses only; unpaid; deferred / profit share). Up to 20 roles per project. Returns the project with its roles and their ids.

Create a new draft project exactly as the Studio's New project does: a title (optional) and whether it is public or private (invite only). The draft is not listed until publish_project. Refused with the Studio's own message when the user's filmmaker profile is not ready (a creator account with a public filmmaker profile, display name and at least one role) or the user already has the maximum number of live projects. Returns the project (same shape as get_project): next are update_project for the details, add_project_role for each role, then publish_project.

Full details of one of the user's own projects, as the Studio editor shows them: every field, the roles with pay and their application counts, the publish checklist with the tool that completes each open item, whether it can be published, previous work and the films that could be listed as previous work, and the public and Studio links. Only the owner can read a project this way; anyone else's answers not found.

The applications to one of the user's projects (the Studio's Applicants tab), newest first, optionally for one role: each applicant's public profile card (name, handle, roles, location, website and social links, public films), their note and links, status, the owner's next moves, and the message thread. Open applications (submitted or shortlisted) by default; status all includes decided, withdrawn and closed ones.

Remove a role from a project. A role that already has applications cannot be removed (mark it filled with update_project_role instead), so nobody's thread disappears.

Change a project's details (the Studio's Details tab): title, logline, description, project type, format, stage, country and city or remote-friendly, shoot dates or dates flexible, links, previous work (the user's own published films, by public id) and its visibility (public or private · invite only). Only the fields given change. Validation and messages are the Studio's own; making a live project public re-runs the publish checklist.

Change one of a project's roles: name, how many people, description, pay, or mark it filled (its pending applications close and the applicants are e-mailed) or open again. Only the fields given change; the role keeps its applications.

Permanently delete a hosted video and its file. Irreversible: always confirm with the user first (name the video) and only then call with confirm set to true.

Full details of one hosted video: title, description, visibility, size, duration, views, player colour, category and its links, plus the direct HLS stream link (hls_url, a .m3u8 for third-party players and channel tools) when one is available and otherwise hls_status (ready, processing, not_encoded, not_included, private, unavailable) with hls_reason saying what is missing. HLS links are only given for public videos with ready adaptive quality versions (paid plans); plays through them count against the owner's bandwidth but record no views or earnings. In urls, share (/player/) is the public link to give out and embed_iframe the embed URL; manage (/video/) is the owner's own editing page, sign-in required, and anyone else opening it is sent to the player page — never hand it out as a share link.

Change a video's title, description, visibility (public/private), player colour or content category. Only the fields given are changed.

The user's filmmaker profile as the Profile page shows it: username (the public handle) and why it cannot go public yet, display name, bio, location, roles, website and social links, whether the profile is public and its public link, plus how many credits from other filmmakers await an answer. The avatar is managed in the Profile page.

Change any part of the user's filmmaker profile: username, display name, bio, location, roles (up to 6, presets or custom), website, per-platform social links and whether the profile is public. Only the fields given change; the Profile page's validation, username rules and uniqueness check apply and its messages come back on failure. Avatar changes stay in the Profile page.

Make a film public on its film page. Refused, with the same message the film editor shows, while the publish checklist is incomplete: title, poster, a ready main film, a price only when it is Buy or rent (a free-to-watch film publishes without one), and the creator's rights confirmation. The first time a film is published the user must agree to this statement, which you read to them in full before passing confirm_rights: true: "I confirm I own or hold every right needed to publish and sell this film, including music, footage, performances and releases from people in it. I accept full responsibility for any claim that it infringes someone's rights, as set out in the Terms of Service – Your warranties (/terms#your-warranties)." A film that already carries a confirmation is not asked again. The checklist comes back with how to finish each open item: update_film or start_film_upload where a tool can do it, publish_film with confirm_rights for the rights row, and the editor link for the poster, which is added in the film editor, not through this connection.

Publish a project: it goes live on its page and, when public, on Projects and Jobs. Refused, with the same message the Studio editor shows, while the checklist is incomplete (title, logline, description, project type, location or remote, shoot dates or dates flexible, at least one role); the answer lists each open item with the tool that completes it (update_project or add_project_role). Also refused by the live-projects cap and while a project is under review. Publishing a closed project reopens it.

The owner's move on an application to one of the user's projects: shortlist, accept or decline, with an optional message posted in the thread afterwards. The applicant is e-mailed, exactly as when the owner decides in the Studio. A decision is final (accepted and declined applications cannot be moved again).

Accept, decline or unlink a credit another filmmaker gave the user (credit_id from list_my_credits). Accepting a pending credit shows the film on the user's public profile; declining a pending one or unlinking an accepted one keeps the name on the film but removes the link to the user's account.

Begin uploading a film's main film or trailer from the user's computer. Files cannot be sent through this connection: the tool returns an upload_url the user opens in their browser (signed in to Vidreno) to pick the file; the upload goes straight to Vidreno's film storage (outside plan storage) and is attached to the film when it finishes, replacing the current file in that slot. Afterwards call get_film to see the new file's state; get_upload_status with the upload_id works too. Links are single-use and expire after about an hour.

Begin uploading a new video from the user's computer. Files cannot be sent through this connection: the tool returns an upload_url the user opens in their browser (signed in to Vidreno) to pick the file; the upload goes straight to Vidreno's storage with the metadata given here pre-filled. Afterwards call get_upload_status with the upload_id to get the finished video and its embed code. Links are single-use and expire after about an hour. This is also the right tool when the user attached the video in the chat unless this AI app can supply a temporary https download URL for the attachment (ChatGPT can; use upload_video_from_chat there).

Check an upload started with start_video_upload, upload_video_from_chat or start_film_upload: awaiting_file (includes the upload_url while it can still be used), uploading, ready (a hosted video comes with its details and a default embed code; a film file with the film and slot it was attached to), expired (start a new upload), or failed (chat imports only; includes failure_reason).

Store a video file the user attached in this conversation as a new hosted video. Only usable when the AI app itself fills in a temporary https download_url and file_id for the attachment (ChatGPT does this). Clients that cannot supply such a URL (including Claude) must not call this tool or try to send the file contents: call start_video_upload instead, which gives the user a browser upload link. Pass the attachment as `file`. The file must be a video of at most 512 MB, and the user's plan must have room for it (the same storage rule as any upload). The transfer runs on Vidreno's side; the tool waits briefly and returns status ready (with the video and its embed code), uploading (keep calling get_upload_status with the upload_id until it is ready or failed), or an error explaining what to do instead. For files above the limit or on the user's computer, use start_video_upload.

The connected creator's account overview: which product it is set up for (creator_mode: Films, or Host & Embed for hosted videos; a preference that shapes what to suggest first, not a restriction on the tools), plan, hosted-video storage used versus the plan limit, how many hosted videos and films they have, and their public filmmaker profile link when the profile is public.

How the user's videos are doing: totals (videos, views, storage), the most viewed videos, the newest uploads and a daily views series for the last N days.

The applications the user has made to other people's projects (the Studio's Applications page), newest first: role, project, status, note and links, whether it can still be withdrawn, the owner's public profile card and the message thread.

Apply to an open role as the user, with their filmmaker profile as the application (the owner sees the public profile card), an optional note and up to 3 links. The apply form's rules apply unchanged: a creator account with a public filmmaker profile, display name and at least one role; one application per role; not the user's own project; up to 20 applications a day. The owner is e-mailed.

Close a live project: its page stays readable with a "no longer looking for people" notice, it leaves Projects, Jobs and the sitemaps, every open role closes and pending applicants are told by e-mail. Always confirm with the user first (name the project) and only then call with confirm set to true.

Turn a film's plain director and cast text lines into credit rows (Director for the director line, Actor for each comma-separated cast name), appended after the existing credits, and clear the lines — the film editor's convert button. Nothing is linked or invited; use update_film_credit afterwards. Returns the full credit list.

Credits that other filmmakers added the user to on their films, pending first: the role and name as written, the film (id, title, status, public page) and the film owner's name. Pending ones await the user's answer (respond_to_credit); accepted ones show on the user's public profile.

What the user's Payouts page shows, read-only: lifetime and this month's earnings split into film sales and ad earnings, the balance (available to cash out, maturing inside the hold window, paid out, in flight), the payout minimum and hold period, the saved payout method in masked form, whether ad earnings are live for this account or still coming soon (with the current ad terms: what advertisers pay per 1,000 views and the share the user keeps after payment-processing fees), a per-film breakdown (sales, refunds, gross, net earnings) and the 5 most recent payouts. Amounts are in cents with a display string. Read-only: to cash out or change the payout method the user opens https://vidreno.com/payouts. Use list_payouts for the full payout history and list_film_sales for individual orders.

Build the HTML embed snippet for a video with the chosen player options (autoplay, muted, loop, controls, corner radius, fullscreen, responsive or fixed size). The snippet keeps the video's own aspect ratio (16:9 when its size is unknown). Also returns the bare iframe URL, the player and share links, and the direct HLS stream link (hls_url, for third-party players and channel tools that take a .m3u8 rather than an iframe) when available, else hls_status and hls_reason explaining what is missing. In urls, share (/player/) is the public link to give out and embed_iframe the embed URL; manage (/video/) is the owner's own editing page, sign-in required, and anyone else opening it is sent to the player page — never hand it out as a share link.

List the user's films (On Demand: free to watch or buy/rent), most recently edited first, with optional search and status filter. Returns public film ids to use with the other film tools. Paginate with page/page_size.

Email (or re-send) the invite for a credit that carries an email address, so the person can claim it with their Vidreno account. The same limits as the app apply: a daily cap per account and no repeat email to the same address for the same film within a day. Returns the invite link too; with link_only it only mints the link (nothing is sent), as the editor's copy-link button does.

Search the open roles on Vidreno Jobs (public, live projects only): by free text, department or exact role, country, remote-friendly, pay type and project type, newest projects first, paged with limit and offset (total counts every match; follow next_offset while has_more is true). Each result is the role with its pay and the project (type, format, stage, location, dates, the owner's public profile card) and the public links. Role ids are for apply_to_role.

The user's cash-out requests, newest first: amount, status (requested, processing, paid or failed with the reason), method, masked destination, requested and paid dates. Read-only; the user requests payouts at https://vidreno.com/payouts. Paginate with page/page_size.

Identify the Vidreno account this connection belongs to. Call this when the user asks which account is connected.

List the user's own projects (crew calls on Vidreno Projects), newest first: status (draft, live or closed), visibility, role count, how many applications are waiting, and the public and Studio links. Also says whether the user can post one (the filmmaker-profile requirements and the cap on live projects). Project ids are for the other project tools.

Set the order of a film's credits: pass every credit_id of the film in the order they should appear.

Post a message in an application's thread as the user, whether they are the project owner or the applicant; the other side is e-mailed, as from the Studio. Returns the whole thread. Not possible once the application was withdrawn.

Take a film off its public page (back to draft). Viewers who already bought or rented it keep their access.

List the user's hosted videos, newest first, with optional search and visibility filter. Returns public video ids to use with the other tools. Paginate with page/page_size. In urls, share (/player/) is the public link to give out and embed_iframe the embed URL; manage (/video/) is the owner's own editing page, sign-in required, and anyone else opening it is sent to the player page — never hand it out as a share link.

Withdraw one of the user's own open applications (submitted or shortlisted). The thread stays readable; a withdrawn application cannot be reopened, so confirm with the user first.