I’ve been using Rebel for almost month now, and this week I hit a milestone: I built my first custom MCP connector from scratch.
The problem: In our AI Academy Session 3 (“Art of the Possible”), we demo what’s possible when AI tools work together. One of the outputs is a custom song with real data baked into the lyrics — generated via Suno. Until now, that meant a manual handoff: Rebel would write the lyrics, I’d copy them into Suno, wait for the track, then come back. It was the last remaining tab-switch in what’s otherwise a fully orchestrated workflow.
The fix: I found a community-built MCP server (CodeKeanu/suno-mcp) that wraps Suno’s API. It runs in Docker and provides 6 tools — generate music, check status, get track info, check credits, and convert to WAV.
What it took:
Signed up for an API key at sunoapi.org (usage-based pricing)
Cloned the repo locally and pointed Rebel at the Python server file
Added the MCP config just a command pointing to python3 server.py with the API key as an environment variable
Tested it — Rebel can now generate music, check progress and retrieve tracks without leaving the conversation
This was my first time adding a connector that isn’t in Rebel’s catalogue, it’s a community MCP, not an official one. The whole process took about 15 minutes including the security check on the repo.
Why this matters beyond music: The point isn’t really about Suno. It’s that any API can become a Rebel tool. If there’s a service you use that requires tab-switching, there’s probably a community MCP for it or you can build one. The pattern is the same: find the MCP, add the config, test it.
This brings my connector count to 26. Next up: ElevenLabs for podcast generation which would make Session 3 a true zero-handoff demo.
Built by Emma Rees. Shared via the Rebels community.