
Compeller
Create and track AI music videos and audio-reactive visuals from songs.
What it can do
What data it sees
Do you need an account
An API key from the service settings is required
Create and track AI music videos and audio-reactive visuals from songs.
How to connect
How to connect Compeller to Claude
The server address to paste into Claude settings:
https://compeller.ai/api/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Compeller to ChatGPT
The server address to paste into ChatGPT settings:
https://compeller.ai/api/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Compeller to Cursor
The server address to paste into Cursor settings:
https://compeller.ai/api/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (30)
Raw names from tools/list. Only developers need these.
| get_capabilities | Get Compeller platform capabilities, supported features, and API version. |
| get_pricing | Get current Compeller subscription plans and pricing. |
| list_styles | List available visual styles for Compeller video generation. |
| upload_media | Get upload instructions for media files (audio, images, video). Returns the upload URL and required headers. Requires API token authentication. |
| search_music | Search Deezer preview tracks by song, artist, or album. Use this when the user provides a song string but no MP3/WAV/FLAC file. |
| create_compel_from_music | Create a compel from a selected Deezer preview track. If the user provides an audio file instead, upload that file and use create_compel. |
| create_compel | Create a Compeller generation job from primary audio media and optional reference media. Returns compel id, status, and links to track progress and retrieve renderings. |
| get_compel | Get the current status, progress, and details of a Compeller generation job. |
| start_render | Start rendering a READY compel with default configuration so an agent can continue to final MP4 without opening the browser UI. |
| list_compels | List all Compeller generation jobs for the authenticated account, newest first. |
| search_compels | Search Compeller generation jobs by title for the authenticated account. |
| list_renderings | List all video renderings for a specific compel. |
| get_rendering | Get details of a specific video rendering. |
| search_media | Search and list uploaded media files for the authenticated account. |
| register_webhook | Register an HTTPS endpoint to receive signed push notifications for compel lifecycle events (compel.ready when renderable, compel.completed, compel.failed). Returns webhook_id and the HMAC-SHA256 signing secret exactly once - store the secret immediately, it is never returned again. Deliveries are signed via X-Compeller-Signature: sha256=<hex> over the raw body. Delivery is at-least-once: a failed delivery is retried with backoff (up to 6 attempts) and every retry carries the same X-Compeller-Event-Id, so dedupe on it. |
| list_webhooks | List all webhook endpoints registered for the authenticated account. Secrets are never returned by this tool. |
| delete_webhook | Delete a webhook endpoint by id. Removes the registration and stops future deliveries. |
| test_webhook_delivery | Synchronously POST a synthetic webhook.test event to a registered endpoint. Uses the same HMAC-SHA256 signature as real deliveries, runs the standard URL safety check at delivery time, and returns {webhook_id, event_id, event_type, delivered, response_status, response_body_preview, latency_ms, error?}. Ignores the endpoint's events subscription - test delivery is always on-demand. Use this to verify your integration before relying on compel.completed / compel.failed events. |
| update_webhook | Update one or more mutable fields on a registered webhook endpoint: url, events, active. At least one of these must be provided. Validation mirrors register_webhook (https-only, <= 2048 chars, URL safety blocklist). Returns the updated endpoint (secret is never returned by this tool - use rotate_webhook_secret for that). |
| rotate_webhook_secret | Mint a new HMAC-SHA256 signing secret for a registered webhook endpoint. The previous secret is invalidated immediately - integrators must update their receiver before the next compel terminal event fires. Returns the new secret exactly once; store it on receipt. |
| cancel_compel | Cancel an in-progress compel. Dequeues it if still queued, otherwise cancels any active external (AI provider) tasks and transitions it to CANCELLED. Idempotent - cancelling an already-CANCELLED compel succeeds. Use to stop a mis-prompted or runaway job before it consumes more render minutes. |
| get_account_credits | Get the authenticated account's render-minute balance and plan: minutes remaining (free + paid), monthly allowance, plan code, and whether the quota is exceeded. Call before starting an expensive render so an agent can make cost-aware decisions. |
| list_lighting_effects | List the COM-497 starter lighting effects available to launch as cues (e.g. "gobo-cycle", "x-move", "dimmer-pulse"). Each effect carries an id, the capabilities it needs, and a launch_contract template. Use the returned id as effect_id for launch_lighting_cue. |
| launch_lighting_cue | Launch a starter lighting effect onto a stage as a live cue (e.g. "gobo-cycle on the stage's 7R beams at speed 0.5"). Pass effect_id (from list_lighting_effects) and optional variables to override effect defaults. Validation is loud: an unknown effect, a launch_contract whose bindings a stage cannot render, or a missing required field is rejected. Returns the active cue including its launch_id, resolved variables, and launch_contract for REACT. REACT executes the cue per-frame; the live strobe slider stays authoritative and is never raised by a launch. |
| list_lighting_cues | List the live (non-stopped) lighting cues REACT is executing, including each cue's launch_id, resolved variables, launch_contract, and feedback. Optionally scope to one stage. |
| get_lighting_cue | Fetch a single live lighting cue by its launch_id, including resolved variables, launch_contract, and REACT feedback. |
| stop_lighting_cue | Stop a live cue by its launch_id. Idempotent - the cue is marked stop-requested so REACT drops it on its next refresh. |
| set_lighting_cue_variables | Update variables on a live cue (e.g. change cycle speed or intensity mid-show). Only the variables you pass change; the rest keep their current values. Stopped cues are rejected. |
| ack_lighting_cue | REACT/BAE acknowledgement for a launch_id. Idempotently records whether the executor accepted or rejected the cue and which executor observed it. |
| report_lighting_cue | REACT/BAE report-back for cue status, active variables, skipped bindings, capability misses, last_frame_at, and errors. |