@remix-re/mcp

Connect your assistant to Remix, a general video-making agent. Create videos from a brief, images, clips, audio, trends, or saved Assets. Generate media and ask Remix to combine it into a finished edit.

Setup

You need Node.js 20 or newer and a Remix API key from remix.re/app/developers. Replace rk_live_... with your key. Billing does not need to be enabled to use MCP. Your account’s existing generation limits still apply. Choose your assistant below, create and copy your key on the developer page, and put it in your local configuration. Keep the key out of chat.

Codex

codex mcp add remix --env REMIX_API_KEY=rk_live_... -- npx -y @remix-re/mcp

Add tool_timeout_sec = 300 under [mcp_servers.remix] in ~/.codex/config.toml so Remix's wait calls have time to return. Run codex mcp list to check the configuration. The full setup guide includes a complete TOML entry.

Claude Code

claude mcp add remix -e REMIX_API_KEY=rk_live_... -- npx -y @remix-re/mcp

Other MCP clients

Add this to your client's MCP configuration:

{
  "mcpServers": {
    "remix": {
      "command": "npx",
      "args": ["-y", "@remix-re/mcp"],
      "env": { "REMIX_API_KEY": "rk_live_..." }
    }
  }
}

Reload your client's MCP connection, then ask “Check my Remix credit balance.” A successful check is free and confirms that your connection works. Copying the configuration alone does not confirm a connection. The response includes your balance, current subscription access, and a Manage billing link. Generation requires an active subscription or approved free month; promotional credits alone do not unlock it. If access has lapsed, use the returned Resubscribe or Update payment method link, then ask the assistant to check again. Existing videos and billing remain readable. Connecting and checking the account are free.

Try it

Choose any starting point: describe a video, attach media to combine, or copy a trend. Remix uses Do it for me by default and makes creative decisions as it works. Say “Ask me first” if you want it to pause for input when needed. There is no extra mode-selection step.

We highly recommend copying a trend or using an Asset with a template for a clear starting structure:

Copy this trend: [paste the link]. Use Sam and Our Bottle from my Remix library. Keep the joke, but set it in our office. Show me the estimate before starting.

Videos typically take 5–30 minutes and cost 1,500–4,000 credits ($15–$40). A trend link and saved Assets are optional. You can start with a brief, upload your own media, or generate images, clips, and audio and pass the resulting files to the video agent:

Combine these product photos, the generated office clip, and this voiceover into a 30-second launch video. End on “Available now.”

Individual media generation and video assembly are billed separately.

Your assistant starts checking progress automatically after submission, including in Ask me first mode. It shows the full plan and every question and choice inline as they arrive. Answer the whole question group and it continues checking after sending your answers. Unanswered questions expire after 30 minutes and Remix decides. Routine unchanged checks stay quiet; a wait timeout does not mean the video failed. If the assistant cannot keep checking, it should say monitoring is paused and keep the video ID so you can ask it to resume.

When the video is ready, use Open in editor for hands-on changes when available, or “Tell me what to change” to request revisions through the agent on the same video. The editor is optional; some outputs may not have an editable project.

Documentation

Read the full guide for workflows, all 24 tools with inputs and examples, model choices, pricing, and troubleshooting. The guide is also available at remix.re/app/developers and through the remix://guide MCP resource.

Environment

| Variable | Required | Purpose | | --- | --- | --- | | REMIX_API_KEY | Yes | Your Remix API key. | | REMIX_API_BASE | No | API URL override for staging. Defaults to https://api.resonate.audio/v1. |

Development

npm ci
npm run lint
npm run typecheck
npm run build
npm test
npm run check:guide-copy

The stdio smoke test needs the build. When editing docs/REMIX_MCP.md, also update ../remix-web-app/public/mcp/REMIX_MCP.md; the copy check verifies that the package and website ship the same guide.

Deployment

The MCP runs locally in each assistant and is deployed by publishing @remix-re/mcp to npm. It does not need a separate hosted server.

Releases use npm trusted publishing with GitHub OIDC. No NPM_TOKEN or other npm publishing secret is required. The release job uses Node.js 24, npm 11.19.1, and id-token: write on a GitHub-hosted runner. Provenance is disabled because this repository is private.

In npm, open @remix-re/mcp → Settings → Trusted publishing, add a GitHub Actions publisher, and enter these case-sensitive values:

| Field | Value | | --- | --- | | Organization or user | Resonate-inc | | Repository | resonate-monorepo | | Workflow filename | remix-mcp-release.yaml | | Environment name | production | | Allowed actions | Enable direct publishing with npm publish |

First release: npm requires the package to exist before a trusted publisher can be configured. If @remix-re/mcp is still unpublished, a maintainer with access to the @remix-re scope must sign in using npm login and publish the first validated release tarball once. The workflow saves this tarball before attempting publication. Then configure the trusted publisher above; future versions publish through GitHub without an npm token. The npm trust prerequisites also require package write access and account 2FA.

To deploy, open Actions → Remix MCP release → Run workflow, select main, and enter the version in remix-mcp/package.json (currently 0.1.1). The equivalent command is:

gh workflow run remix-mcp-release.yaml --ref main -f version=0.1.1

Pushing a tag named remix-mcp-v<version> also publishes that commit. The workflow checks version consistency, guide synchronization, lint, types, tests, and MCP schemas before packaging and publishing. It saves the release tarball as a workflow artifact and verifies the published version on npm. If publishing fails with an authentication error, check the npm trusted publisher fields and direct-publish permission, then re-run the failed job. After changing the workflow itself, start a new run from main; re-running an older run uses its original workflow and commit.

npm versions are immutable. For subsequent releases, bump package.json, package-lock.json, src/version.ts, both versions in server.json, and the guide's front-matter version in both copies before merging and deploying. If a run fails in Verify npm release, choose Re-run failed jobs to retry only verification. Do not re-run the successful publishing job or start another release of that version; a published version cannot be overwritten.