Connect Idea to Motion to Kiro and you can ask for a video the same way you ask for anything else. Kiro writes the script, plans each scene and writes the animation code; we synthesize the voiceover, time it to the words, render the animation and hand back an MP4. It launches MCP servers as local processes rather than calling them over HTTP, so the mcp-remote bridge carries your key to the server for you.
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
Generate a connection key
Add it to Kiro
.kiro/settings/mcp.json (per project) or ~/.kiro/settings/mcp.json (user)
{
"mcpServers": {
"ideatomotion": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.ideatomotion.com/mcp",
"--header",
"Authorization:Bearer vai_YOUR_KEY"
],
"disabled": false,
"autoApprove": []
}
}
}Generate a key above to replace vai_YOUR_KEY.
mcp-remote bridge carries your key over HTTP.The exact names Kiro reads, and what happens when one of them is wrong.
Kiro reads its MCP servers from a JSON file — .kiro/settings/mcp.json. It can live in either of two places, and the per-project one only applies inside that project. 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, Kiro 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 from Kiro's agent panel the same way you ask for a change to the code — the tool calls run beside your editor, and you approve the plan there.
Type it into the agent panel, in the same thread you use for code.
“Make a 30-second vertical explainer about the feature I just finished.”
What comes back
The ways this goes wrong, and most of them go wrong silently.
Kiro → MCP Servers → Edit config opens the right file; editing it directly works too. Kiro spawns stdio processes rather than calling HTTP, so the entry runs the mcp-remote bridge locally and carries your key over it. The entry also ships a disabled flag — if the panel has switched the server off, that is where it shows, and a disabled server looks identical to one that failed to load.
Check the names in .kiro/settings/mcp.json. 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, Kiro 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 paste the new key over the old one in the config and reload Kiro. Paste the whole vai_ string including the prefix; the old key can be revoked from the same panel.
This can live in two places: .kiro/settings/mcp.json (per project) and ~/.kiro/settings/mcp.json (user). A per-project file only applies while you are working in that project, so an entry in the wrong one reads exactly like a config Kiro is ignoring. Put it in the user-level file if you want it everywhere, and reload Kiro either way.
Kiro launches MCP servers as local processes, so this entry runs npx -y mcp-remote on your machine and needs Node on the PATH Kiro 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 Kiro. Silent motion graphics need no voice key at all, so "make it a silent motion graphic instead" is a valid way past this.