# Postal Developers

- [Overview](/): Build on Postal with the REST API and the MCP server.
- Getting started
  - [API keys](/getting-started/api-keys): Create a key, choose its scopes, rotate and revoke it.
  - [Quickstart](/getting-started/quickstart): Your first three requests in five minutes.

- **REST API**
- REST API
  - [Conventions](/api): Base URL, authentication, the response envelope, errors, pagination and limits.
  - [Versioning](/api/versioning): What the /api/v1 prefix guarantees, how to read the version you are on, and how deprecations are announced.
  - [Tracks](/api/tracks): List, get, count, upload and update tracks. Find duplicates and trace submissions.
  - [Track versions](/api/track-versions): Replace a track's audio while keeping its ID, and read, switch, label or delete the versions in its history.
  - [Natural-language search](/api/search): Rank your whole library against a description of the music you need.
  - [Tags and auto-tagging](/api/tagging): The tag taxonomy, editing tags, and the AI tagging pipeline.
  - [Playlists](/api/playlists): Create and manage playlists, add tracks, reorder, and get the public link.
  - [Composers](/api/composers): Writer, producer and publisher records attached to tracks.
  - [Analytics](/api/analytics): Weekly dashboard, per-track engagement and top-track rankings.
  - [Briefs](/api/briefs): Calls for submissions you own, and what came in.
  - [Webhooks](/api/webhooks): Signed HTTP callbacks when tracks, composers and shares change.
  - [Key management](/api/key-management): Create, scope, rotate and revoke keys, and read usage, from a dashboard session.
  - [Platform API](/api/platform): Read-only, cross-account reporting for partners that run file requests on Postal.

- **MCP**
- MCP server
  - [MCP server overview](/mcp): Give Claude, Cursor or any MCP client direct access to your Postal library.
  - [Connect a client](/mcp/connect): Add the Postal MCP server to Claude, Claude Code, Cursor or any other MCP client.
  - [Tool reference](/mcp/tools): Every tool the Postal MCP server exposes, with parameters, the REST endpoint behind it and the API key scope it needs.
  - [Example prompts](/mcp/prompts): Things to ask an assistant once Postal is connected, and which tools they exercise.
  - [Auth and scopes](/mcp/auth-and-scopes): How the MCP server authenticates, and which scopes a key needs for which tools.
  - [Versioning](/mcp/versioning): How the MCP server is versioned, where to read the version, and what changes between releases.
  - [Compact mode](/mcp/compact-mode): How responses are trimmed by default, and how to get the full payload.
  - [Troubleshooting](/mcp/troubleshooting): Common connection and permission problems.

- **Guides**
- Use cases
  - [Use cases](/use-cases): What people build on Postal, and which parts of the API each one uses.
  - [Catalogue sync](/use-cases/catalogue-sync): Keep an external system of record and a Postal library in step.
  - [Sync and pitching](/use-cases/sync-pitching): From a brief to a shareable shortlist in three calls.
  - [Tagging pipeline](/use-cases/tagging-pipeline): Tag every upload automatically, review what the model is unsure about, and feed corrections back.
  - [Reporting](/use-cases/reporting): Weekly digests, leaderboards and partner reporting.
  - [AI assistant](/use-cases/ai-assistant): Work in a Postal library from Claude, Cursor or any MCP client.
- [Changelog](/changelog): Dated changes to the REST API and the MCP server.