Connect HeyMotion to an AI Assistant BETA

#Overview

This guide sets up the HeyMotion MCP server so an AI assistant like Claude can render graphics for you. There are two paths, and you only need one:

• Remote connector — no install, fastest to try, has hourly rate limits.
• Local install — runs on your own machine, unlimited and private, needs a quick setup.

If you are not sure what MCP is or which tools it exposes, start with the HeyMotion MCP Overview.

#Before You Begin

For the remote connector you just need an AI assistant that supports custom MCP connectors (for example, Claude). For the local install you need Node 22+ and Google Chrome (macOS, Linux or Windows). Nothing here requires a paid plan — MCP access is included with the Founding and Studio plans.

#Path A — Remote Connector (no install)

This is the quickest way to start. Renders happen on HeyMotion's servers.

1. Open your assistant's Settings.

2. Go to Connectors and choose Add custom connector.

3. For the server URL, enter:

   https://mcp.systemprompt.co/mcp
   

4. Leave the OAuth fields empty — no client ID or secret is needed.

5. Save the connector, then enable it in your chat so the assistant can call its tools.

That's it. You can now ask the assistant to list templates and render clips. Remember the rate limits: 8 renders/hour, 20 seconds max per clip.

#Path B — Local Install (unlimited, private)

The local server renders inside your own copy of Google Chrome. There are no rate limits, everything stays on your machine, and finished files download to your browser's Downloads folder.

#1. Install the server

Run this in your terminal:

curl -fsSL https://heymotion.io/install-mcp.sh | bash

This installs HeyMotion to ~/sp-motion-studio. You need Node 22+ and Google Chrome (macOS, Linux or Windows).

#2. Register it with your assistant

You have two options.

Option 1 — Claude Desktop config. In Claude Desktop, go to Settings → Developer → Edit Config and add the HeyMotion server, pointing at the installed server file:

{
  "mcpServers": {
    "motion-studio": {
      "command": "node",
      "args": ["~/sp-motion-studio/tools/mcp/server.mjs"]
    }
  }
}

Option 2 — command line. Register it with:

claude mcp add

Follow the prompt to point it at node ~/sp-motion-studio/tools/mcp/server.mjs.

#3. Restart and confirm

Restart your assistant so it picks up the new server, then confirm it can see the HeyMotion tools (for example, ask it to list templates). Renders now run locally in your Chrome and files land in your Downloads folder.

#Example Prompts

Once connected, you can describe the graphic in plain language. A few that work well:

• "List the Data templates and pick one for a subscriber-count stat."
• "Make a 9:16 big-counter — 1.2M views in 30 days."
• "Render a preview of the end card with my brand, then render the full clip if it looks right."
• "Set my accent color to #E63946, then re-render that counter."

The assistant will call list_templates, describe_template, render_preview, and render_clip as needed, and can read or update your brand with get_brand and set_brand.

#Options and Settings

#Best Practices

Lock your brand before a batch of renders — either sign into the web studio so your kit syncs, or ask the assistant to call set_brand at the start of the session. Use render_preview while you iterate and only render_clip when the look is final; on the remote connector that also keeps you under the 8 renders/hour, 20 seconds max per clip cap.

#Common Mistakes

Filling in the OAuth fields on the remote connector will stop it from connecting — leave them empty. On the local install, a missing requirement is the usual culprit: the server needs Node 22+ and Google Chrome (macOS, Linux or Windows), and rendering opens your Chrome, so Chrome must be installed. If the assistant can't see the tools after setup, restart it so it reloads the connector list.

#Troubleshooting

• The assistant doesn't see the tools → confirm the connector is enabled in the chat (remote) or restart the assistant (local).
• Renders fail on the local install → check that Google Chrome is installed and you are on Node 22+ and Google Chrome (macOS, Linux or Windows).
• You keep hitting a render cap → that is the remote rate limit (8 renders/hour, 20 seconds max per clip); switch to the local install for unlimited rendering.

If you're still stuck, contact support.

#Related Articles

Back to the HeyMotion MCP Overview.