Idea to Motion is a standard remote MCP server, so anything that speaks the protocol can drive it. If your client isn't listed, use the bridge command below — it works with any client that can launch a local process.
mcp-remote config entry and reload the client.Generate a connection key if this client needs one, then add the server.
Pick your app
Chat apps
Editors & IDEs
Terminal
Set up Any other client
Generate a key, then add the server.
Generate a connection key
Add it to Any other client
npx -y mcp-remote https://api.ideatomotion.com/mcp --header "Authorization:Bearer vai_YOUR_KEY"
Generate a key above to replace vai_YOUR_KEY.
url + an Authorization: Bearer header.mcp-remote is only needed for clients that can spawn stdio processes but not call HTTP.The exact names Any other client reads, and what happens when one of them is wrong.
Any other client reads its MCP servers from a JSON file. The entry goes under mcpServers. Those names are not what every other client uses, and getting one wrong is not an error, it is silence: the file parses, Any other client starts, and the server never appears.
Narration is synthesized on your own ElevenLabs, Cartesia or Sarvam AI key. Silent motion graphics need none.
Idea to Motion generates the voiceover on your own text-to-speech account. Add an ElevenLabs, Cartesia or Sarvam AI key — it's stored encrypted and never shown again. Rendering is blocked until a key is connected.
Where the line between your assistant and the platform falls, and why it falls there.
Ask for a video the way you ask your assistant for anything else — the tool calls run inline, and you approve the plan wherever that client shows you tool results.
Type it wherever that client takes instructions, once it lists the server's tools.
“Make a 30-second vertical explainer about how our onboarding works, for Instagram.”
What comes back
The ways this goes wrong, and most of them go wrong silently.
Then skip the bridge. A direct entry — the server URL plus an Authorization: Bearer header — is fewer moving parts and no local process to keep alive. mcp-remote exists for clients that can spawn stdio processes but cannot call HTTP themselves. If you are not sure which yours is, the Ask your agent tab hands it the facts and lets it write its own config.
Check the names. The entry belongs under mcpServers, and the URL is an ARGUMENT to mcp-remote rather than a field of its own, so its position in the args array matters. These differ between clients — some read mcpServers, some servers, some context_servers — and a wrong one is not an error: the file parses, Any other client starts, and the server is simply never loaded. Copy the snippet in step 1 rather than adapting one from another client's documentation.
A key that is wrong, truncated or revoked gets a 401, and most clients report that as a failed connection rather than as an auth problem. Keys are shown once and stored hashed, so there is no way to read an old one back — generate a fresh one in step 1, then re-run the npx -y mcp-remote command with the new key and reload Any other client. Paste the whole vai_ string including the prefix; the old key can be revoked from the same panel.
Any other client launches MCP servers as local processes, so this entry runs npx -y mcp-remote on your machine and needs Node on the PATH Any other client inherits — which is not always the PATH your shell has. The -y flag fetches the bridge on first use, so the first launch is slower than every later one. Note that the header argument has no space after the colon, because mcp-remote splits its arguments on spaces.
Narration and transcription run on your own ElevenLabs, Cartesia or Sarvam AI key rather than ours, so a narrated or recorded video needs one connected — step 2 on this page, or the set_voice_key tool from inside Any other client. Silent motion graphics need no voice key at all, so "make it a silent motion graphic instead" is a valid way past this.