Connect Qwen to After Effects
Yes. Qwen can drive After Effects, through Qwen Code. The model does not connect to anything on its own — Qwen Code is the client, it speaks MCP, and it discovers Prism's OAuth automatically. About two minutes, once.
| Qwen surface | Connects | How |
|---|---|---|
| Qwen Code CLI | Yes | qwen mcp add, or httpUrl in settings.json |
| Any OAuth-capable client running Qwen | Yes | OpenCode, Cline, Cursor |
| Qwen Chat · chat.qwen.ai | No | No MCP client |
| Qwen via the API | No | You would be building your own client |
Connect Qwen Code to After Effects
httpUrl, not url
Qwen Code infers the transport from the field name: command is stdio, url is SSE, httpUrl is streamable HTTP. Prism needs httpUrl. Put the address under url and Qwen opens an SSE connection that never completes, which looks like Prism is down.
https://live.oneprism.io/after-effects — the same for everyone, and it holds no secret.-s user puts it in ~/.qwen/settings.json so it works in every project. Drop the flag to scope it to the current one.
qwen mcp add --transport http prism https://live.oneprism.io/after-effectsSame result, if you would rather edit the file. Leave headers out entirely — Prism issues no keys, so there is nothing to put in one.
{
"mcpServers": {
"prism": {
"httpUrl": "https://live.oneprism.io/after-effects"
}
}
}dynamic_discovery, so it reads Prism's OAuth configuration from the server itself and opens your browser on the first call. There is nothing to register and no client ID to paste.Or skip the commands: paste the address into the agent itself and ask it to add the MCP server. It can configure its own client.
Qwen Code is a fork of Gemini CLI but the two have diverged here: Qwen wants
httpUrl, and Antigravity explicitly
rejects that key and wants serverUrl. A config copied between them will not work.
Prove it works
- "Tell me about my current composition." proves the read path
- "Stagger these layers by two frames and ease them out." proves the write path
- "Transcribe this audio layer into subtitles." proves Prism AI
More in your first prompts.
If it does not work
| What you see | What it usually means |
|---|---|
| It hangs on connecting | The address is under url, so Qwen is trying SSE. Use httpUrl |
| It tries to launch a program | The address is under command. That field is for stdio servers |
| It asks for a token | A headers block was added. Remove it and let OAuth run |
| Every call is refused | The browser sign-in was never completed. Trigger a call again |
| Qwen cannot reach Prism | The panel is closed. It has to be open in After Effects |
| It connects but sees no composition | No comp is active. Open one |
More in troubleshooting.
If the client was already open, quit it and open it again
Save the address, then run the client's sign-in step. If your AI client was open before the address existed and does not show Prism, quit it and open it again: most clients load their connections at launch. Then open a composition and ask for it by name.
Common questions
Yes. Prism is an MCP server for Adobe After Effects, published as io.oneprism/after-effects in the official MCP Registry. It reads the live composition and writes native layers and keyframes back, rather than generating a script for you to paste and run.
Yes, through Qwen Code. Qwen is the model and Qwen Code is the client, and it is the client that speaks MCP. Qwen Chat has no MCP client, so it cannot connect.
httpUrl. Qwen Code infers the transport from the field: url means SSE and httpUrl means streamable HTTP, which is what Prism speaks. This is the most common setup mistake on this client.
No. Prism issues no keys. Qwen Code discovers Prism's OAuth configuration from the server and signs you in through your browser with the account you already have.
Yes, and that is deliberate. You keep your own Qwen plan, and Prism takes nothing for the model that drives it, which is why Pro carries unlimited MCP actions.
No. Your .aep files, footage and comps stay on your machine. Only the structure of the open composition and the instruction you asked for make a round trip.
Related
Kimi
Connect Kimi K3 to your live After Effects project with the Prism MCP server. Two commands in Kimi CLI, one browser sign-in, and real editable keyframes back.
DeepSeek
Connect DeepSeek Harness to your live After Effects project. Install an OAuth MCP plugin, sign in through the browser, and get real editable keyframes back.