Connect DeepSeek to After Effects
Yes. DeepSeek can drive After Effects. Everything in DeepSeek Harness is a plugin, including its MCP client — and that is the part that matters. Swap the built-in client for one that does OAuth and DSH connects like anything else. About five minutes, once.
| DeepSeek surface | Connects | How |
|---|---|---|
DSH + dsh-mcp-manager | Yes | Browser OAuth, PKCE, dynamic client registration |
DSH + dsh-oauth-mcp-client | Yes | Same flow, drop-in for the native client |
| Any OAuth-capable client running DeepSeek | Yes | OpenCode, Cline, Cursor, Zed |
| DSH, built-in client only | No | Static headers only, no OAuth flow |
| DeepSeek app · chat.deepseek.com | No | No MCP client |
Connect DeepSeek to After Effects
The built-in MCP client is not the one you want
@deepseek-ai/dsh-mcp-client accepts a static headers block and nothing else. Prism issues no keys, so there is nothing to put in it. Install an OAuth plugin instead — DSH is built for exactly this.
https://live.oneprism.io/after-effects — the same for everyone, and it holds no secret.dsh-mcp-manager or dsh-oauth-mcp-client. Both replace the built-in client with one that can complete a browser sign-in, and both keep the token across restarts.headers block out entirely — there is no token to put in it.mcp__prism__* and the model can call them like local ones.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.
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 |
|---|---|
| DSH asks for an API key | The built-in client is still active. Install an OAuth plugin |
| The server is added but every call is refused | The browser authorisation was never completed |
Tools do not appear as mcp__prism__* | The server failed to register. Check the plugin's own log |
| DeepSeek 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. With an OAuth MCP plugin, DeepSeek Harness connects to Prism and drives your live composition. You can also run DeepSeek as the model inside any client that already does browser sign-in, such as OpenCode, Cline or Cursor.
It passes a static headers block and has no OAuth flow of its own. Prism authorises through the browser and issues no keys, so there is no token to place in a header. It is a gap in that one client, not a restriction in Prism, and a plugin closes it.
No. Keys were deliberately removed: a key leaks, cannot be scoped to a person, and has to be rotated by hand. Browser sign-in is what makes the MCP address safe to publish in the first place.
No. The tools, the allowance and the results are identical whichever model drives them. Stronger models plan better, which shows up as fewer wasted calls rather than different capability.
Yes, and that is deliberate. You keep your own DeepSeek plan, and Prism takes nothing for the model that drives it, which is why Pro carries unlimited MCP actions.
Related
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.
More clients
Prism works in any client that supports remote MCP servers with browser sign-in: OpenCode, Cline, Cursor, Windsurf, Zed, VS Code, Qwen Code and more.