Integration

Spinitron integration

Spinitron is the playlist and program-schedule service used by radio stations. Read a station's spins (the tracks played, with artist, song, release, label and classical-music metadata), its playlists, its scheduled shows and upcoming episodes, and the personas (on-air DJ and host names) behind them, filtered by date range, show, playlist or persona. One write is available: log a spin, the way a station automation system does. The fields and expand query options are not offered. Authentication is the station's API key from the Automation & API page of the Spinitron Admin menu, sent as a Bearer token.

Connect Spinitron How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Spinitron.Built from the 9 Spinitron tools below, on the connection you add once.

What you can do with Spinitron

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Spin, 3 operations

get_spinGet spinGETGet one spin (a played track) by id: artist, song, release, label, year, genre, medium, DJ note, request and local flags, ISRC and UPC, and classical-music fields.
list_spinsList spinsGETList the tracks the station has played (spins), optionally within a datetime range or for one playlist or show. Only past spins are returned. Each spin carries artist, song, release, label, genre, year, cover art and classical-music fields.
log_spinLog spinPOSTLog a spin (a played track) into the station's spin table, the way an automation system does. artist and song are required; start, duration, release, label, genre, composer and isrc are optional. Returns the spin that was created.

Persona, 2 operations

get_personaGet personaGETGet one persona (an on-air DJ or host name) by id: name, HTML biography, since-year, email, website, image and links to the persona's shows.
list_personasList personasGETList the station's personas, the on-air DJ and host names, with biography, photo and links to their shows. Filter by name; paginated with count and page.

Playlist, 2 operations

get_playlistGet playlistGETGet one playlist by id: show, persona, start and end time, title, category, episode name and description, and whether automation created it. Fails with 404 when it starts more than 1 hour in the future.
list_playlistsList playlistsGETList the station's playlists, newest first, optionally within a datetime range or for one show or persona. Only past playlists are returned (up to 1 hour ahead); set future to 1 for upcoming public playlists, soonest first.

Show, 2 operations

get_showGet showGETGet the next episode of a show by show id: start and end time, duration, title, category, HTML description, image and links to its personas and playlists. Fails with 404 when the show does not exist or all its episodes have aired.
list_showsList showsGETSearch the station's program schedule. With end, returns every episode of the matching shows up to that time (an upcoming-episodes grid); without end, only the first upcoming episode of each show. start and end may be at most 1 hour in the past.

Use Spinitron from Claude Code, Cursor or Codex

Connect Spinitron in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Spinitron operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Spinitron

Create your workspace
Sign up free. Nothing to install.
Connect Spinitron once
Add your Spinitron connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.