Docs

Connect an AI assistant

Ask Claude, Cursor or ChatGPT to make a demo video of your app, check on it and share it, right from the chat.

Made with ClipYourSaaS

Make a video from the chat

Connect your assistant. The steps for Claude Desktop, Claude Code, Cursor and ChatGPT are below. Sign in, choose your workspace and approve.
Ask for a video of a website by its address, for example “Make a walkthrough video of https://app.example.com showing how to invite a teammate”. The assistant passes the address to create_video. If the site isn’t one of your apps yet, we add it to your Apps for you, named after its address. Only owners and admins can add a site this way. Next time anyone in your workspace asks for a video of the same site, we reuse that app. If the assistant doesn’t know whether the site needs a sign-in, it asks you. Apps you already have work too: the assistant finds them with list_apps.
If the site needs a sign-in, the assistant gives you a sign-in link. Anyone in your workspace who asks gets the sign-in link, and it works only for this video’s app. Open it in any browser: you don’t need to be signed in to ClipYourSaaS there. Choose Sign in to followed by your site’s address, and a secure browser opens in a window called Sign in to your app. Sign in as you normally would, finish on a page only signed-in users can see, then choose I’m signed in. The link works for 30 minutes, and only once: after you’ve signed in with it, it stops working. Until then, you can open it again.
We then run the app’s connection test automatically. When it passes, the app is Ready and your video starts by itself. You can close the tab. If the test fails, the video is cancelled, free, and the app’s page says why. A site that needs no sign-in gets the same test before its first video.
Ask it to check back later. Videos up to 2 minutes usually take 10–15 minutes; longer ones up to 2 hours. It looks the video up with get_video. When the video is ready, it gives you the watch link (the video’s page on ClipYourSaaS, for your workspace’s members) and the download links.
Ask it to share the video. share_video makes a public, unlisted link, with downloads off unless you ask for them.

A link acts for the person who asked: it stops working if they leave the workspace, or if the assistant connection or API key that asked is revoked. Only owners and admins can Connect an app on its page in the dashboard. Until someone signs in, the video’s page shows Waiting for you to sign in.

A video waiting for a sign-in costs nothing. We reserve the most it can cost, but nothing is charged unless it runs. If no one signs in within 30 minutes, it is cancelled, free. Only 3 sign-in links can be open at once in your workspace: a newer one cancels the oldest waiting video, free. When a saved sign-in expires, your next video waits for a new sign-in in the same way.

A video may change what its app allows, as set on the app’s page: View only, Limited changes or Any changes. An app added from the chat starts as View only, unless you ask for more. In the chat you can ask for less, which applies to that one video, or for more, which changes the app’s setting as on its page in the dashboard. Only owners and admins can ask for more. Any changes needs your agreement in the chat. The assistant shows you this sentence: “I'm happy for this account to be changed, including permanently. I'm responsible for those changes.” It sends the request again with that sentence, word for word, only after you agree. Without it, the request is refused. A refused request changes nothing. See What a video may change.

Videos made this way are paid from your workspace’s credits and show up in the dashboard like any other. To see or remove a connection, open Settings → Connected assistants and choose Revoke. With nothing connected yet, that page’s Set up an assistant button brings you here.

Set up your assistant

The ClipYourSaaS MCP server is at https://clipyoursaas.com/mcp. The assistant signs you in with OAuth, so there is no key to copy. Any member of a workspace that has bought credits (a pack or a plan) can connect one, and its videos are always paid from the workspace's credits.

Assistants must send you back to an address that uses https, or http on localhost or 127.0.0.1. The assistants below all do.

Claude Desktop

Open Customize → Connectors, choose Add, then Add custom connector. Name it ClipYourSaaS, paste https://clipyoursaas.com/mcp and continue. If Claude asks which OAuth client to use, choose Register automatically. Claude opens a browser window to sign you in. The connector works in Claude on the web too.

Claude Code

claude mcp add --transport http clipyoursaas https://clipyoursaas.com/mcp

Then run /mcp in Claude Code and choose clipyoursaas to sign in.

Cursor

Add this to ~/.cursor/mcp.json, or to the project's .cursor/mcp.json, then sign in from Cursor's MCP settings:

{
  "mcpServers": {
    "clipyoursaas": {
      "url": "https://clipyoursaas.com/mcp"
    }
  }
}

Cursor receives the sign-in on http://localhost:8787. If something else is using that port, Cursor falls back to a cursor:// address, which we don't accept; free the port and sign in again.

ChatGPT

ChatGPT adds custom MCP servers as developer-mode apps, on the plans that offer them. Turn on Developer mode in Settings → Security and login, then create an app (or connector) with the MCP server URL https://clipyoursaas.com/mcp and OAuth authentication, and sign in when ChatGPT asks. ChatGPT renames these menus from time to time; if you can't find them, look for the option to add a custom app or connector.

After you sign in, you choose the workspace the assistant will work in; only workspaces that have bought credits (a pack or a plan) are listed. The consent screen then shows:

the assistant's name, marked unverified name, because any app can call itself anything;
Returns to: where approving sends you back, which is the part to check. An assistant that runs on your computer, like Claude Code or Cursor, shows as an app on this computer;
a warning when the site the assistant says it is from doesn't match where it sends you back. If you see it and didn't expect it, choose Deny;
an optional daily credit cap: the assistant can't start a video that would take its spending past the cap that day (UTC).

Approve, and the assistant can create and view videos in that workspace as you.

What the assistant can do

list_apps: Your connected apps, whether each is ready to record, and what a video may change in it: its change mode and whether a reset link restores it first. For an app whose sign-in has expired, anyone in the workspace can also start a video to get a sign-in link.
list_voices: The narration voices, with samples.
create_video: Start a video, paid from credits. length_seconds is a maximum, or "auto" for as long as it takes (up to 10 minutes); narration can be turned off for a silent video (25% less). changes says what the video may change: view_only, limited (describe the changes in allowed_changes) or any. Without it, the video may change what the app allows. any needs confirm_any_changes, set to the exact sentence you agreed to in the chat; without it the answer is confirmation_required, and nothing is created or changed. To film a site, pass url (the page to start on) instead of app_id: we use your app for that site, or add one, which gets the request’s changes, view_only if none. sign_in says whether the site needs a sign-in. When it does and we have none, the video waits, and the answer carries sign_in_url, a sign-in link (it works for 30 minutes), or, in the rare case no link could be made, sign_in_needed with the app’s page.
get_video: Check on a video; when it is ready, get its download links. Square and vertical follow a few minutes after it is ready. While a video waits for a sign-in, its stage is waiting_for_sign_in, with sign_in_url while its link is open or, when no link could be made, sign_in_needed and dashboard_url (the app’s page). While it waits for its new app’s connection test, its stage is waiting_for_app_test. When it is ready, it also gives the video’s page on ClipYourSaaS (watch_url), for your workspace’s members.
list_videos: Recent videos, newest first.
cancel_video: Cancel a queued or running video. It stops at once. It’s free until we’ve rehearsed the demo, then costs 0.25 credits. It answers charged_credits: what this cancel was charged. A repeat cancel is never charged again. The fee never applies to free videos. A ready video isn’t cancelled: its square and vertical keep rendering.
share_video: Create or update the video’s unlisted share link. Downloads are off unless you ask for them (allow_downloads).
relearn_app: Forget what ClipYourSaaS learned about an app and learn it again: what each section holds and when you’d use it, and an About the app we drafted (never notes you wrote). Owners and admins only. The app shows learning until it finishes, usually within a few minutes; videos for it wait.

Videos up to 2 minutes usually take 10–15 minutes; longer ones up to 2 hours. Ask the assistant to check back rather than wait. The API's rate limits apply to each connection.

An app in Limited or Any changes without a reset link keeps the changes a video makes, several times over. The assistant sees this in list_apps and should tell you before it starts such a video. Set the mode and the reset link on the app's page in the dashboard. If a reset link fails during a video, list_apps shows reset_failing and create_video answers reset_link_failing until you test the link on the app's page.

An app you sign in to that shows needs_reconnect can be signed in again in the dashboard, or through a video’s sign-in link.

Revoking access

Open Settings → Connected assistants in ClipYourSaaS and choose Revoke. The assistant loses access at once. Owners and admins can revoke anyone's connections and change their caps. When someone leaves the workspace, their connections are revoked automatically. A connection that goes unused for 30 days has to sign in again.

Prefer scripts? Start with an API key in the API quick start.