What is an MCP server?

MCP (Model Context Protocol) is an open standard from Anthropic that lets AI agents interact with external tools and data sources. TAP's MCP server gives agents access to 14 tools covering campaigns, contacts, pitches, and outcomes -- the full music PR workflow.

Can an AI agent use TAP without a human?

TAP provides the infrastructure for agents to list contacts, run enrichment, draft pitches, and log outcomes. But TAP's philosophy is clear: AI assists, you decide. Pitches are always drafted for review, never auto-sent. The agent does the legwork, you make the calls.

Which AI agents work with TAP?

Any agent that supports the Model Context Protocol (Claude Code, Cursor, Windsurf, and others) can connect to TAP's MCP server. The REST API works with any HTTP client, so custom agents built with the Anthropic SDK, OpenAI API, or any other framework can integrate too.

Do competitors have APIs or MCP servers?

No. We audited every major music PR tool -- Musosoup, SubmitHub, Groover, Haulix, Meltwater, Cision, CoverageBook, and HubSpot (as used by agencies). None have a music-PR-specific public API, MCP server, llms.txt, or OpenAPI spec. TAP is the only music PR platform with programmatic access.

TAP Is the First Music PR Tool an AI Agent Can Actually Use

Every music PR tool on the market has the same problem: they're locked boxes.

SubmitHub, Groover, Musosoup, Haulix -- none of them have a public API. None have an OpenAPI spec. None have an MCP server. If you want to build on top of them, connect them to your workflow, or let an AI agent interact with your contact data, you can't.

TAP is different.

What TAP exposes

TAP has a REST API (7 endpoints), an MCP server (14 tools + 3 resources), an OpenAPI 3.1 specification, and machine-readable documentation (llms.txt and llms-full.txt).

An AI agent connected to TAP can:

List and search contacts across your workspace -- filter by name, outlet, genre, or platform type
Import contacts in bulk -- up to 500 per request, with email validation, deduplication, and idempotency
Validate email addresses -- SMTP verification, catch-all detection, disposable email flagging, and suggested corrections
Run AI enrichment -- 14 data points per contact including role detail, genres, submission guidelines, best timing, and BBC station detection
Draft pitches -- context-aware drafts that reference each contact's submission preferences, with tone variants
Log outcomes -- track who replied, who added the track, who declined
Get an action queue -- today's prioritised follow-ups, stale contacts, and pending pitches

That's the full music PR workflow, available programmatically.

Why this matters

The music PR industry is about to change. AI agents are getting better at research, drafting, and coordination. The agencies that survive will be the ones whose tools can actually participate in that workflow.

Right now, if you ask an AI agent to "prepare outreach for my next campaign," it hits a wall the moment it needs to interact with your PR software. The agent can't pull your contact list, can't check enrichment status, can't draft pitches with the right context.

With TAP, that wall doesn't exist.

The MCP server

The Model Context Protocol is an open standard that lets AI agents interact with external tools. TAP's MCP server exposes the full campaign lifecycle:

Campaign tools -- list campaigns, get detailed stats including contact counts and pitch success rates.

Contact tools -- search and filter your contact database, get enrichment detail and relationship history.

Pitch tools -- generate AI-drafted pitches that are already aware of each contact's submission guidelines, preferred timing, and genre focus.

Outcome tools -- log results and get a prioritised action queue for the day.

If you use Claude Code, connecting is one config block:

{
  "mcpServers": {
    "tap": {
      "command": "npx",
      "args": ["tsx", "packages/tap-mcp/src/index.ts"],
      "env": {
        "TAP_SUPABASE_URL": "...",
        "TAP_SUPABASE_KEY": "..."
      }
    }
  }
}

The REST API

For custom integrations, TAP's REST API covers contact management, AI enrichment, email validation, and API key management.

Authentication uses workspace-scoped API keys with granular scopes: contacts:read, contacts:write, validate, enrich, or * for full access.

The API supports batch operations (500 contacts per import, 100 emails per validation, 50 contacts per enrichment), idempotency keys for safe retries, and dry-run mode for validation without side effects.

Full documentation: /developers | OpenAPI spec

What TAP won't do

TAP's philosophy hasn't changed: AI assists, you decide.

The API and MCP server give agents access to your data and tools. But pitches are drafted for review, never auto-sent. Outcomes are logged, never fabricated. The action queue suggests, never acts.

This isn't a limitation. It's the whole point. An AI agent that can send emails on your behalf without review is an agent that can damage relationships you spent years building. TAP draws that line clearly.

The competitive landscape

We audited every major music PR and media relations tool. The results were stark:

| Tool | Public API | MCP Server | llms.txt | OpenAPI Spec | | --- | --- | --- | --- | --- | | TAP | Yes | Yes | Yes | Yes | | Musosoup | No | No | No | No | | SubmitHub | No | No | No | No | | Groover | No | No | No | No | | Haulix | No | No | No | No | | Meltwater | No | No | No | No | | CoverageBook | No | No | No | No |

The gap is real. When AI agents start being used to manage PR campaigns -- and they will -- TAP is the only tool they can actually interact with.

Getting started

Sign up free -- no card required
Go to Settings > API Keys and create a key
Make your first request:

curl https://totalaudiopromo.com/api/v1/contacts \
  -H "Authorization: Bearer tap_ak_your_key_here"

Or connect the MCP server and let your AI agent handle the rest.

Developer documentation →