Skip to content
Last updated

Postal integration

Postal is a music library platform for organizing, tagging, and sharing tracks, stems, and playlists.

Agen.co connects to Postal through Postal's own hosted MCP server as an Official connector. Each user authorizes with their own Postal API key, and agents can work with that user's library, playlists, and submission briefs.


Prerequisites

  • A Postal account with an API key. Create one in Postal under Settings → Integrations, then keep it available for the authorization step below.

Connect Postal in Agen.co

  1. In the Agen.co portal, go to Connectors → My connectors and click Add connector.

  2. In the Select connector drawer, search for Postal and select it. The Add Postal panel opens.

  3. Fill in the field:

    FieldRequiredDescription
    Instance SlugYesPrefixes each imported tool as slug__tool, so several instances of the connector can coexist. Prefilled with postal. Use lowercase kebab-case. You can change it later from the connector's settings.
  4. Click Connect. Postal opens in a new tab, and the panel shows Waiting for authorization — complete it in the opened tab…

  5. On the Postal tab, which reads Paste your API key to connect your account, enter the API key from Postal's Settings → Integrations page and click Connect. Unlike most Official connectors, this step pastes a key rather than signing in through Postal itself.

  6. Back in Agen.co, the panel switches to Select the tools to import from Postal. Every tool is toggled on; turn off any you don't want to import, then click Add.

The connector is created and its tools imported only when you click Add. If you close the panel before that, nothing is saved, even though the Postal tab reported success.

Authorize each user

Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls a Postal tool, the call returns an authorization link instead of a result. The user opens the link and pastes their own Postal API key the same way. After that, the user's tool calls run against that user's own Postal library.

Once connected, Postal appears under My connectors with 39 tools spanning:

AreaWhat it covers
TracksListing, searching (by filter or by natural-language description), reading, counting, updating metadata, uploading from a URL, and finding exact duplicates
Track versionsListing, uploading, activating, renaming, and deleting audio versions of a track
TaggingReading the tag taxonomy, setting tags, and triggering, waiting for, reviewing, and applying AI auto-tagging suggestions
PlaylistsListing, reading, creating, updating, reordering, and adding or removing tracks
ArtworkUploading cover art for a track
Composers and shareholdersListing, counting, reading, creating, updating, and deleting composer records
AnalyticsA weekly activity dashboard, engagement stats for specific tracks or playlists, and top tracks by a chosen metric
Submissions and briefsTracing where a track was submitted, and listing briefs and their submissions

Enabling the Postal connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.

Additional resources