Overview

Postal is where artists, producers, publishers and labels keep their unreleased music: organised, tagged, shared and pitched. These docs cover the two ways to work with a Postal library from outside the app.

🔌

REST API

JSON over HTTPS at api.postal.music, authenticated with an API key. Tracks, tags, playlists, composers, analytics, briefs and webhooks.

🤖

MCP server

A hosted Model Context Protocol server at mcp.postal.music. Connect Claude, Cursor or any MCP client to your library in two minutes.

Pick a path

You want to…	Start with
Ask an assistant about your catalogue, tag tracks, build playlists in conversation	Connect the MCP server
Sync tracks and metadata between Postal and your own system	Quickstart, then Tracks
Find music for a brief from code	Natural-language search
React to changes in a library	Webhooks
Report on a partner platform's file requests and sign-ups	Platform API

Base URLs

Surface	URL
REST API	`https://api.postal.music/api/v1`
MCP server	`https://mcp.postal.music/mcp`
App (API keys, scopes, webhooks)	`https://postal.music/settings/integrations`

One key, both surfaces

An API key created in the Postal app works for the REST API directly and is the credential you connect the MCP server with. Scopes on the key bound what either surface can do. See API keys.

For AI agents reading this site

Every page has a Markdown version behind the copy button at the top, and the whole site is available as plain text at /llms.txt and /llms-full.txt. The MCP tool catalog with JSON schemas is at https://mcp.postal.music/tools.