Skip to main content
Skip to content
TAPStart your release

For your agent

Your agent, working with TAP

The agent you already use reads your campaign, drafts pitches, logs outcomes, and surfaces what needs you. Everything it does lands in your approval queue before anything moves.

TAP drafts and queues. Replies, plays and coverage land back against each contact.

What your agent can do

Plain-language capabilities

These are the things you can ask your assistant to do. It reads your workspace, makes suggestions, and writes drafts. It does not take action until you confirm.

Search your contacts

Your assistant can search your contact list, pull up past conversations, and fill in missing details like outlet and contact history.

Draft pitches

Give it a release and a contact list. It writes a tailored pitch for each person and puts them in your queue.

Run your release campaign

Create a campaign, add contacts, log plays and replies. Your assistant reads the full history before it drafts anything, so suggestions are grounded in the real record.

Queue everything for your approval

Every draft, every proposed send, every suggested action lands in your queue first. The assistant proposes; you decide.

Summarise results

Once replies and coverage come in, your assistant can pull a summary of what worked and build the bones of a wrap report.

Remember what happened

TAP stores what happened across every release. Your assistant reads that history before it drafts anything, so suggestions come from the real record, not a blank page.

Full technical reference on /developers.

How it works in practice

Three scenes from a real campaign week

Scene 1

Your morning brief

Overnight, your assistant catches up so you do not have to

While you sleep, radio plays come in, replies land, and the campaign moves. In the morning your assistant reads all of it, works out who still needs a follow-up, drafts the messages, and parks them in your approval queue. You open TAP, see what is ready, and decide what goes out.

Scene 2

Drop a list, get pitches

Hand over a contact list and come back to polished drafts

Paste in a list of contacts or import a spreadsheet. Your assistant checks them against your existing database, fills in missing details where it can, and drafts a tailored pitch for each one based on the campaign brief. You review the drafts, adjust anything you want to change, and approve the ones ready to send.

Scene 3

Log outcomes, get the report

As plays and replies come in, the report builds itself

Log a WARM play, note a positive reply, record a coverage mention. Your assistant tracks all of it against the campaign and, when you need a campaign update, assembles the numbers and narrative from the actual record rather than asking you to remember what happened.

The one thing that never changes

TAP drafts and queues. It never sends on its own.

TAP can analyse, suggest, draft, and queue. TAP never auto-sends without explicit human approval.

Every pitch draft, every proposed follow-up, every suggested send lands in your approval queue first. You review it, adjust it if needed, and press send yourself. Your relationships stay yours.

Three ways to connect

Three ways to connect the agent you already use to TAP

1

Through Claude, Cursor, or any AI tool

Install the TAP connector once and your agent can talk to TAP directly. Best if you already use Claude, Cursor, ChatGPT, or another agent you trust and want to extend it.

2

From the command line

The TAP CLI gives you quick access to contacts, campaigns, and skills without opening a browser. Useful for batch operations or if you prefer working in a terminal.

3

Via the API

Every action in TAP is available through the REST API. Right choice if you are building a custom integration or want to connect TAP to another tool in your stack.

Connect in 5 minutes

From zero to first command

This is the setup for connecting Claude Desktop, Cursor, or any MCP-compatible assistant. The API and CLI routes are on /developers.

  1. 1

    Add the TAP connector

    In Claude Code, run the command below. Using Claude.ai or Claude Desktop instead? Settings then Connectors then Add custom connector, and paste https://totalaudiopromo.com/api/mcp as the URL. Cursor and most other MCP clients take the same URL in their MCP settings.

    Terminal
    claude mcp add --transport http tap https://totalaudiopromo.com/api/mcp
  2. 2

    Sign in when asked

    Your assistant opens a TAP sign-in page the first time it calls a tool. Sign in with your TAP account and approve the connection. No API key to create or paste -- this is OAuth, the same kind of sign-in you already use for other connected apps.

  3. 3

    Run your first command

    Once connected, ask it something like:

    “List my active campaigns and draft tomorrow's follow-ups.”

    TAP will return your campaigns, check reply and play status, and put draft follow-ups in your approval queue.

  4. 4

    Prefer a local server and your own key?

    Fallback for a client without OAuth support, local development, or working offline. Create a key in Settings then API Keys, run the TAP MCP server on-demand via npx, and point your assistant config at it.

    Terminal (fallback)
    npx -y @totalaudiopromo/tap-mcp@latest
    claude_desktop_config.json (fallback)
    {
      "mcpServers": {
        "tap": {
          "command": "npx",
          "args": ["-y", "@totalaudiopromo/tap-mcp@latest"],
          "env": {
            "TAP_API_KEY": "tap_ak_live_..."
          }
        }
      }
    }
Or use the REST API directly
curl https://totalaudiopromo.com/api/v1/campaigns \
  -H "Authorization: Bearer $TAP_API_KEY"

Full API reference and all available scopes are on /developers.

TAP drafts and queues. You open it and see what is ready.

Your assistant does the reading, matching and drafting. Replies, plays and coverage land back against each contact and release.

Ready to connect your assistant?

Signing up is free, and your free release can connect an agent.