Bring the library
into your editor.

Connect to the hosted MCP.

Claude Code:

claude mcp add --transport http cave-motion https://cave-motion.darkknightcave.workers.dev/mcp

Codex configuration:

[mcp_servers.cave_motion]
url = "https://cave-motion.darkknightcave.workers.dev/mcp"

Cursor MCP configuration:

{
  "mcpServers": {
    "cave-motion": {
      "url": "https://cave-motion.darkknightcave.workers.dev/mcp"
    }
  }
}

All three tools are read-only. The connection supplies recipes; your agent builds the animation in your project.

Run the package locally.

The server runs on your machine and makes no network calls after npm downloads it. These commands pin version 0.1.2, so a later release cannot change the catalog your agent sees.

Claude Code:

claude mcp add cave-motion -- npx -y @darkknightcave/motion-mcp@0.1.2

Codex configuration:

[mcp_servers.cave_motion]
command = "npx"
args = ["-y", "@darkknightcave/motion-mcp@0.1.2"]

Cursor MCP configuration:

{
  "mcpServers": {
    "cave-motion": {
      "command": "npx",
      "args": [
        "-y",
        "@darkknightcave/motion-mcp@0.1.2"
      ]
    }
  }
}

Running npx by hand prints nothing and waits for MCP messages on standard input. Your editor starts it for you. Client documentation: Claude Code, Codex, Cursor.

Build from source.

To work on the server itself, clone the standalone Motion Library repository and build it.

git clone https://github.com/DKC-Engineering/motion-library.git
cd motion-library
npm ci
npm run build

From that directory, add the built server to Claude Code with an absolute path so it also works in other projects. For Codex and Cursor, set command to node and pass the same absolute path as the only argument.

claude mcp add cave-motion -- node "$PWD/dist/src/stdio.js"

Try the two-call workflow.

search_motion({"query":"a product launch film"})

prepare_motion({
  "id": "feature-launch",
  "brief": "Show three features of my scheduling product using supplied screenshots.",
  "customization": {"accent":"#35745e","aspectRatio":"16:9","duration":12}
})

Your agent receives the prepared prompt, dependencies, credit, and review steps. Ask it to implement the result in your project. It will need your final text, real data, and cleared assets.

What runs where.

The Streamable HTTP endpoint is https://cave-motion.darkknightcave.workers.dev/mcp. It supplies the same catalog as the local package. Generation and rendering happen in your coding environment.

Local stdio and hosted protocol tests are separate from testing inside each editor. Check the release verification report for the environments actually exercised.