MCPOverview

MCP Server

The Slipstream MCP server lets AI assistants talk to the Slipstream catalog through structured tools. Search tracks in plain language, build playlists, soundtrack a video, clip or extend a track, allowlist a channel against Content ID claims, issue a licence, and preview audio inline.

It implements the open Model Context Protocol. Any MCP-compatible client works: Claude Desktop, Claude Code, claude.ai web, ChatGPT, and others.

Server URL

https://mcp.slipstreammusic.com/mcp

Open to any authenticated Slipstream user. Auth happens through OAuth on the first call, no API keys to manage.

What you can do

The server exposes 56 tools across ten areas:

  • Search and discovery. Natural-language search, similar-track lookup by reference link or track ID, creative-brief shortlists, genre and mood browsing.
  • Tracks. Full track details, stems and alternate versions, download links.
  • User and library. The signed-in user’s profile, liked tracks, likes.
  • Playlists. Create, read, update, reorder, delete, download as a ZIP, share, and search public playlists.
  • Editing. Cut a track down to a clip, or extend it to a longer target duration by seamless looping.
  • Soundtrack a video. Upload a video, get tracks that fit it, render the final mix.
  • AudioVerify. Identify every piece of music in a video, tell whether the subscription covers each one, and surface any registered label such as Epidemic Sound.
  • Channels and allowlist. Register a creator’s channels or individual videos so Content ID doesn’t claim their own licensed uploads.
  • Licensing. Turn a chosen track into a filled licence agreement priced from the enterprise’s rate card.
  • Inline UI. Six widgets — track player, soundtrack studio, AudioVerify uploader, clip editor, Audio Extender, and licence preview. See Rendering widgets.

Public catalog tools work without authentication. Anything that touches a user’s library, uploads media, or issues a licence uses the OAuth flow described in Authentication.

When to use MCP vs the REST API

Both surfaces wrap the same backend. Pick by what you’re building.

  • MCP is for AI agents that need to reason about music in plain language, no glue code. Add the URL to your client config and the agent can search, curate, and act.
  • REST API is for products you write code for. Direct, versioned, JSON. See the API Reference.

Get connected

The fastest path: open the Quickstart and pick your client. Connecting takes about a minute.

Once connected, jump to Available tools to see what your agent can do.

Authentication

OAuth 2.1 with PKCE. Your MCP client opens a browser tab the first time you use a Slipstream tool. You log in with your Slipstream account (the same one you use on the web), approve, and the client gets a token. From then on, calls run on your behalf, with your existing permissions.

Any Slipstream user tier can connect: Free, Commercial, Subscriber, Enterprise. What you can do through MCP matches what you can do on the web.

Server-to-server. If your backend calls the MCP server directly, you can authenticate with a partner token instead of the browser flow and identify each of your end users with an X-User-ID header. See Server-to-server.

Quickstart