Compeller
Turn songs into AI music videos and audio-reactive visuals by creating Compels, starting renders, and tracking completion from your agent.
Overview
Compeller MCP is a Build-phase MCP server that creates and tracks AI music videos and audio-reactive visuals from songs.
What is this MCP server?
- Discover styles and pricing, search music, create and track Compels
- Start renders and retrieve finished videos via MCP tools
- Register signed webhooks for render completion events
- Remote endpoint https://compeller.ai/api/mcp (Streamable HTTP JSON-RPC)
- Discovery tools work without auth; generation requires Compeller API token
- Server version 0.5.0 per connector metadata
- Unauthenticated discovery; authenticated generation and account operations
Community signal: 1 GitHub stars.
What problem does it solve?
You want agent-driven music visuals but manually clicking through Compeller breaks automated content workflows.
Who is it for?
Indie musicians, content founders, and marketers automating promo videos or reactive visuals from existing tracks.
Skip if: Builders who need only static album art with no video render pipeline or Compeller account.
What do I get? / Deliverables
Your agent can quote styles, create Compels, run renders, fetch videos, and subscribe to completion webhooks programmatically.
- Created and tracked Compels
- Rendered music video files retrievable via MCP
- Webhook endpoints notified on completion
Recommended MCP Servers
Journey fit
How it compares
Hosted generative video MCP API, not a local ffmpeg SKILL.md skill.
Common Questions / FAQ
Who is ai.compeller/compel for?
Creators and solo builders using MCP agents to produce music-linked AI videos without hand-operating the Compeller UI for every render.
When should I use ai.compeller/compel?
During Build when you integrate Compeller into content pipelines, prototypes, or launch asset generation with programmatic create-and-track flows.
How do I add ai.compeller/compel to my agent?
Add mcpServers.compeller with url https://compeller.ai/api/mcp and Authorization Bearer YOUR_COMPELLER_API_TOKEN (or X-API-Token), then call tools from your MCP client.