Connect Kimi to After Effects
Yes. Kimi can drive After Effects, through Kimi Code CLI. K3 is the model and the CLI is the client, and it is the client that speaks MCP. Kimi Code has a real OAuth flow, which is what Prism needs. About two minutes, once.
| Moonshot surface | Connects | How |
|---|---|---|
| Kimi Code CLI | Yes | kimi mcp add --auth oauth |
| Kimi app · kimi.com | No | No MCP client |
| K3 via the API | No | You would be building your own client |
Connect Kimi to After Effects
Do not omit --auth oauth
Without it Kimi expects an API key, and Prism issues none. The server is added but every call is refused.
https://live.oneprism.io/after-effects — the same for everyone, and it holds no secret.Run this in your terminal. --transport http is the streamable HTTP transport, which is what a remote server needs, and --auth oauth is what tells Kimi to open a browser rather than look for a key you do not have.
kimi mcp add --transport http --auth oauth prism https://live.oneprism.io/after-effectsRun kimi mcp auth prism. Your browser opens, and if you are already signed in to Prism there it completes straight away. Kimi caches the token, so this is the only time you do it.
kimi mcp auth prismOr skip the commands: paste the address into the agent itself and ask it to add the MCP server. It can configure its own client.
K3 is the model and Kimi Code is the client. Any other client running K3 works too, as long as it speaks MCP and signs in through a browser.
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 |
|---|---|
| The server is added but every call is refused | kimi mcp auth prism was never run, or the browser step was abandoned. Run it again |
| Kimi looks for an API key | --auth oauth was left off when the server was added. Remove it and add it again with the flag |
| Kimi 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 |
The longer list is 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 Kimi Code CLI. K3 is the model and the CLI is the client, and it is the client that speaks MCP. Any other client you run K3 in works too, as long as it supports remote MCP servers with OAuth.
Use --transport http. Prism is a remote server reached at an address, so there is nothing on your disk for stdio to launch.
No. There is no API key anywhere in Prism. The --auth oauth flag tells Kimi to open a browser and sign you in with the account you already have.
Yes, and that is deliberate. You keep your own Kimi 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
Gemini
The Gemini app has no MCP client. Connect Gemini to your live After Effects project through Google Antigravity: one serverUrl entry, one browser sign-in.
Qwen
Connect Qwen Code to your live After Effects project with the Prism MCP server. One qwen mcp add command, OAuth in the browser, and real editable keyframes back.