Postal DevelopersMCP server overview
Give Claude, Cursor or any MCP client direct access to your Postal library.
The Postal MCP server exposes your library to AI assistants through the Model Context Protocol. Once connected, an assistant can search your tracks by describing the music, read and write tags, build playlists, look up composers, check listening analytics and trace where a track has been submitted.
It is a hosted, remote server. There is nothing to install or run locally.
| Server URL | https://mcp.postal.music/mcp |
| Transport | Streamable HTTP (stateless) |
| Auth | OAuth 2.1 with PKCE, or an X-API-Key header |
| Tools | 39 (see the tool reference) |
| Version | 1.6.0, semantic versioning (see Versioning) |
| Live catalog | GET https://mcp.postal.music/tools |
What it can do
Search by description
"Find me a warm, downtempo instrumental around 90 BPM with no vocals" ranks your whole library against the brief.
Tag at scale
Trigger AI tagging, review the suggestions, apply or correct them. Corrections train the tagging model.
Build playlists
Create, reorder and share playlists from a conversation. Public links come back ready to paste.
Read the numbers
Weekly dashboard, per-track engagement and top-track rankings, with date ranges.
Manage composers
Keep shareholder records (PRO, IPI, publisher) in sync with your other systems.
Trace submissions
See every brief a track went to, and every submission a brief received.
How it fits together
Every tool call is translated into one or more requests against the REST API using the API key you connected with. The server never stores your audio, and the key's scopes bound what an assistant can do.