Warp · Terminal

Warp + Motion

The agentic terminal, where MCP servers are added from a settings panel rather than a file you go and find. Point it at Motion and one sentence becomes a finished animation, rendered in your own browser.

No registrationNo watermarkNo paywall

Setup

Connect Warp to Motion

One endpoint, no key and no account. This is the part that differs between clients — a different file in a different place, and half of them name the same field differently. Pairing, underneath, works the same way wherever you are, and there are two of those depending on whether you have Motion open.

MCPhttps://motion.frapea.com/mcp

1
Open MCP settings
Settings → Agents → MCP servers, or the warp://settings/mcp deep link. Warp takes a small JSON object rather than a whole config file.
2
Paste the server in
The dialog takes the same shape as the file at ~/.warp/.mcp.json, so a block copied from any other MCP client pastes straight in.
~/.warp/.mcp.json
```
{
  "mcpServers": {
    "motion": {
      "url": "https://motion.frapea.com/mcp"
    }
  }
}
```

Then, the same for every client

Pair the session with Warp

Two ways in, and the only thing that decides between them is whether you have a Motion tab open right now. Neither needs a key or an account.

If Motion is already open

Carry the code to your agent

1Click Connect MCP, top right. The panel shows a line beginning Connect me to Motion with code, with eight characters like K7M4-P2Q9.
2Paste that whole line into your agent — the sentence, not just the code. It is worded so the agent knows which tool to call and what to pass it.
3Good for ten minutes, and once. The code stops working the moment it is spent.

Open Motion

If it is not

Let the agent start without you

1Say start a Motion session for me. Worded so it does not collide with the line above — that one carries a code, and an agent given the same words without one will try it, fail, and have to back out.
2It can compose immediately — you do not need the tab to exist yet. Open the link when you want to watch, or when it asks you to.
3Anything that has to SEE the result, or touch your photos, waits for that tab. The agent knows to wait rather than to nag.

Then say what you want in one sentence. The frames appear in the tab while you keep working wherever you were.

When it doesn’t take

Two things go wrong, and it is almost always one of them

The MCP section is not where the guide saysIt moved. Settings → Agents → MCP servers, or the warp://settings/mcp deep link.

The JSON is rejectedWarp takes the same mcpServers wrapper as the config file, not a bare object — a block copied from any other client pastes in as-is.

Neither of those? The endpoint answers a plain tools/list over POST. If that comes back, the server is fine and the problem is in the config — paste this page into Warp and let it work out which line.

What it gets you

Why this pairing, and not just any of them

It will do something with the file afterwards, because it is a terminal — the render becomes a step in a job rather than the end of one.

Adding the server is a form in the app, and it takes the same JSON any other client would — so a config you already have pastes straight in.
Warp's agent runs shell commands as part of the same job, so it can render the piece and then move, rename or open the result for you.
Useful for release work: cut a build, then ask for the title card announcing it, without switching tools.

What you just handed it

16 tools, and one of them is looking at the result

Warp now has the whole set: it writes the composition as code rather than filling in a template, renders real frames and checks them, and never has to receive your footage to know what is in it.

All 16 tools Warp can call

What comes back

One sentence to final animation

Each of these was a single line said to an agent, rendered by the same runtime Warp would be driving. They change as you read — point at one to play it.