---
title: Set up invideo in Cursor
description: Add the invideo skills to Cursor, sign in once in the browser, and have Cursor's agent generate video, voice and music and edit it on a real timeline you can watch live.
---
Your agent in Cursor gets the invideo skills and the CLI, opens your projects by URL, generates the shots, voices and music a video lacks, and edits it all on a timeline you watch live in the browser. In Cursor, invideo runs through the CLI first.

## Set up

Add the invideo skills to your project. The agent then drives invideo through the CLI in its terminal, like Claude Code and Codex do.

```bash
npx skills add invideoio/skills
```

The skills hold how to connect, the work loop, the cost rule, and the steps for each kind of video. On your first video request the agent installs the invideo CLI, a single binary with no sudo, and opens a browser tab for you to sign in.

<Steps>
<Step title="Add the skills">
Run the line above in your project. You see the invideo skills in your project's skills folder.
</Step>
<Step title="Ask for a video">
Give the agent a video job. It installs the CLI with the install script and runs `invideo auth login`. A sign-in tab opens in your browser.
</Step>
<Step title="Approve in the browser">
Sign in and choose the workspaces the agent may use. Come back to Cursor. It carries on, and `invideo auth status` shows your name.
</Step>
</Steps>

You can also install the CLI yourself, before the first job.

```bash
curl -fsSL https://agents.invideo.io | sh
invideo --version
invideo auth login
```

On Windows, install with the PowerShell line on [invideo for AI agents](/agents).

### The Cursor Marketplace plugin, for MCP

The invideo plugin on the Cursor Marketplace is the MCP route. Click **Customize**, search `invideo`, then click **Install**. The plugin adds the invideo MCP server to Cursor and nothing else: no skills, no CLI. Use it when you want the tools in the chat without a terminal. Pick the CLI or MCP for a session, not both. Over MCP the agent has no skills, so it reads the rules from [invideo for AI agents](/agents) and from `get_help`.

## Sign in

With the CLI, `invideo auth login` opens the browser and waits for you to approve. Sign in and choose the workspaces the agent may use.

Where no browser can open, on ssh or in a container, the agent uses a device code.

```bash
INVIDEO_NO_BROWSER=1 invideo auth login
```

It prints a link and a code. Open the link on another device and enter the code. Your agent never asks you to send the code back, and never asks for a password.

## First prompt

Start with a prompt that proves the connection works.

```text
Use invideo to show me my projects.
```

Then give it a real job. Name the folder with your files.

```text
Make a new invideo project called "Release notes video". Upload the
screen recordings in ./recordings, cut them on a branch, add a title
for each one and a short generated opening shot. Tell me the price
before you spend, and show me the frames before you export.
```

The agent replies with project and timeline URLs. Open them to watch the edit land.

Your agent runs a dry run first. For any call that costs 1 credit or more, it tells you the price and waits for your yes. A call under 1 credit runs without asking, and your agent tells you what it cost.

## If something goes wrong

Most problems come from the install path or the sign-in.

| Symptom | Fix |
| --- | --- |
| The Marketplace plugin is installed, but the agent has no skills | That plugin carries only the MCP server. Add the skills with `npx skills add invideoio/skills` for the CLI path. |
| The agent says `invideo` is not found after the install | The install script wrote `~/.local/bin/invideo`. Run it by its full path, or add that folder to `PATH`. |
| CLI exit 4, not signed in | Run `invideo auth login`, or the device code line above. |
| The sign-in tab never opened | Run `INVIDEO_NO_BROWSER=1 invideo auth login` and open the link it prints. |
| The agent cannot see a workspace | Run `invideo auth login` again and choose that workspace in the browser. |
| Avoid: the agent asks for your code or password | Instead: you approve in the browser, and the agent waits. |
| Avoid: the agent uses the CLI and the MCP plugin together | Instead: pick one for the session. |

## Next

- [invideo for AI agents](/agents), the rules your agent follows
- [Check your video before you say it is done](/how-to/check-your-video)
- [Know the cost before you spend](/how-to/cost-before-you-spend)
- [CLI commands and flags](/reference/cli)