Cue for AI
Cue speaks MCP.
Connect your AI to Cue and it works your catalog like you would — researching artists, keeping EPKs current, and firing off personalized, trackable pitches. Here's the whole flow.
The gist
Cue is an MCP server. Point an MCP client — Claude, or anything that speaks the protocol — at it, approve one prompt, and your AI can read and write your real workspace: the same EPKs, pitches, and contacts you see in the browser. No export, no copy-paste, no second copy of the truth drifting out of date.
No copy-paste, no export. Your AI works on the same live workspace you see in the browser.
Connect it once
In your MCP client's connector settings, add a custom connector pointed at:
https://cue.re/api/mcpThe client discovers the rest on its own and shows you a Connect screen naming the workspace it's about to touch. Approve it and you're live — the grant is scoped to that one workspace, and you can pull it any time from your account.
The one idea: EPK, then pitches
Everything downstream rests on one distinction. An EPK is the artist's durable record — one per artist, the material your AI researches and keeps current: the artist name, the assets and photos, the credits and quotes. A pitch is aimed at a single recipient, and it writes its own story — its hook, its press angle, its note are the pitch's own words, not borrowed prose. The EPK lends the artist name and assets, and on the public page it backfills any kit field the pitch doesn't set itself.
Your AI researches it and keeps it current. The durable material lives here once — the artist name, the assets, the record.
Each pitch writes its own story. The EPK lends the artist name and assets — and any kit field a pitch doesn't set still renders the EPK's value on the public page, so updating the EPK moves every un-overridden field at once.
The payoff: durable facts live once on the EPK — update it when a placement lands and every un-overridden field moves across your pitches — while each pitch stays about the person you're sending to: the story angle, the note, the focus track, the single ask.
What a full run looks like
A typical session, start to finish. You talk; your AI calls the tools.
- 1Researchyour AI digs into the artist, press, DSPs
- 2Build the EPKupsert_artist_epk — the durable one-sheet
- 3Pitch per contactcreate_pitch — one trackable link each
- 4Senda managed cue address or your own domain
- 5Watch it landget_pitch_analytics — opens + plays
“Research Perfect Traveler — press, DSPs, credits — and build out their EPK. Keep it specific and un-hyped; don't invent any quotes.”
“Make a pitch of the Spring '26 sync reel for a music supervisor at a prestige-TV show — lead with the instrumental, flag it's one-stop, and set the CTA to license.”
“Which pitches got opened this week, and what did people actually play?”
Every tool, grouped
Grouped by job. You never call these by hand — your AI picks them — but here's a map of the main tools so you know what it can reach.
list_releasesfind an artist's EPK idget_press_kitread the current kitupsert_artist_epkwrite research to the EPK — merges by defaultresolve_listen_linksone streaming link → verified where-to-listen on every DSP
create_pitchspin up a personalized, trackable pageupdate_pitchenrich or edit onelist_pitchessee everything you've sentget_pitchread one backget_pitch_analyticswho opened, what they playeddelete_pitchretire one
import_contactsadd researched contacts + provenanceverify_contactscheck deliverabilitylist_contactsbrowse the booksuppress_contacthonor an opt-out
enable_managed_sendingclaim your <prefix>@pitch.cue.re — zero DNScreate_sending_identitysend from pitch@yourlabel.comverify_sending_identitycheck DNS + status
create_sequence1–3 threaded touches, preflightedlaunch_sequencefire — capped, windowed, carefullist_threadsreplies, classified by intentreply_to_threadanswer through cue, threaded
upsert_briefcapture a real or inferred askassemble_cataloguerank the catalog — explainable, honestcreate_cataloguea playable /c page for the briefpromote_to_leadconversation → deal pipelineget_cue_sheetpre-filled writers, splits, PROs
Sending
Two ways to put pitches in inboxes. enable_managed_sending claims your own <prefix>@pitch.cue.re address instantly — zero DNS, display-named as you, and every reply or forward to that address lands back in your Cue inbox. Prefixes are yours for good and never re-issued. For heavy senders, create_sending_identity sets up a from-address on your own domain (pitch@yourlabel.com) and verify_sending_identity walks the DNS — your name, your reputation, your reply identity.
Good habits
- Durable facts on the EPK, the story on the pitch. Assets, credits, and quotes live once on the EPK; each pitch writes its own hook and note for its one recipient.
- Specific over hyped. Real quotes, real numbers, real placements — never adjectives, never an invented attributed quote.
- One pitch per recipient. Each gets its own unguessable link and its own analytics bucket, so you see who's actually engaged.
- Give contacts a provenance. When your AI imports a contact, have it record where the address came from — it's your defensible basis to email them.
- Let analytics steer the follow-up. get_pitch_analytics shows opens and plays; a second nudge to someone who replayed the hook beats a blast.