mixetape is an MCP server at https://mixetape.com/mcp (Streamable HTTP), authenticated with
an API key in the Authorization header.
Set it up in your agent
Step-by-step guides: Claude Code, Codex, Cursor and OpenCode.
Any other client
Any client that speaks Streamable HTTP works. The shape most clients take in their config:
{
"mcpServers": {
"mixetape": {
"type": "http",
"url": "https://mixetape.com/mcp",
"headers": { "Authorization": "Bearer mxt_…" }
}
}
}What the agent sees
The server introduces itself with how to start — list_accounts, then create_post — and
lists only the tools the key’s permissions allow. Each tool’s description says what
it does, which permission it needs, and what to call next; a failed call answers with a plain
error the agent can act on (the channel needs reconnecting, a field is missing…).
Times are ISO 8601 with an offset, so the agent never guesses a timezone.
Connecting channels
With the channels permission, the agent can add a channel for you:
connect_channel
{ "platform": "facebook" } returns a sign-in url and a state. The agent gives you the
link; open it in any browser, sign in with the account that owns the channel, and allow
access. The link works once, for 10 minutes.
get_connection
The agent follows the attempt with the state: pending until you finish, then done
with the channels connected — or error with the reason.
choose_channels (sometimes)
When the sign-in reached several new channels — your Facebook Pages, say — the answer is
choose, with the list. The agent asks you which to add and passes their
platformAccountIds to choose_channels. Channels you already had just get fresh access.