Integration

Project Broadcast integration

Project Broadcast is a business texting (SMS, MMS and voicemail drop) platform. An agent can search, create, update, import, archive and delete contacts, send a text to one contact or a broadcast to many, enroll contacts in campaigns and edit campaign events, manage tags, Smart Lists (static or query-driven), keywords, trackable links, landing pages, templates and custom fields, and read the account's credits and settings. Sending tools text real people's phones and spend credits (1 per text, 2 per voicemail drop). Contact records are personal data. Not exposed: partner integrator routes (they need an integrator key), bundle import, and deprecated search filters. Authentication is an API key created under Account, Security, API Keys, sent in the x-api-key header.

Connect Project Broadcast How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Project Broadcast.Built from the 70 Project Broadcast tools below, on the connection you add once.

What you can do with Project Broadcast

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Search, 9 operations

search_campaignsSearch campaignsPOSTSearches the account's campaigns (automated and drip text sequences) by name, page by page, returning each campaign's id, name and type.
search_contactsSearch contactsPOSTSearches contacts with filters (tags, campaign, area code, opt-out flags, birthday, custom fields...) page by page. Returns contact records: names, phone numbers, emails and addresses (personal data).
search_keywordsSearch keywordsPOSTSearches the account's keywords (words contacts text to opt in or trigger automations) page by page, with their aliases, description and validity dates.
search_landing_pagesSearch landing pagesPOSTSearches the account's landing pages by name, page by page, with their title, description and public URL.
search_smart_list_contactsSearch smart list contactsPOSTLists the contacts currently in a Smart List, page by page (the membership from its last evaluation; the query is not re-run). Contact records are personal data.
search_smart_list_keywordsSearch smart list keywordsPOSTLists the join keywords linked to a Smart List, page by page.
search_smart_listsSearch smart listsPOSTSearches the account's Smart Lists by name, page by page, with each list's query state and contact count.
search_templatesSearch templatesPOSTSearches the account's message templates page by page (filter by content type, such as voicemail drops): name, text, media and whether each is ready to use.
search_trackable_linksSearch trackable linksPOSTSearches the account's trackable links by name, page by page, with their URL, slug and auto-tag.

Add, 4 operations

add_contact_to_campaignAdd contact to campaignPUTEnrolls a contact in a campaign so the contact receives its scheduled messages (eventDate is required for event campaigns). Campaign messages text a real person and spend credits.
add_smart_list_contactsAdd smart list contactsPUTAdds contacts to a Smart List by id and returns the list with its updated membership. Sends no message.
add_smart_list_keywordsAdd smart list keywordsPUTLinks join keywords to a Smart List so contacts who text them are added automatically. Refused when the list is query-driven (clear its query first).
add_tag_to_contactsAdd tag to contactsPUTAdds a tag to several contacts and returns the tag with a count and a subset of the tagged contacts.

Contact, 4 operations

create_contactCreate contactPOSTCreates a contact (phone number required) with optional name, email, address, birthday, notes, tags, opt-out flags and custom field values. Contact records are personal data. Creating one sends no message.
delete_contactDelete contactDELETEPermanently deletes a contact.
get_contactGet contactGETReturns one contact found by id, phone number (digits only) or email: name, phone, email, address, tags, opt-out flags and custom field values (personal data).
update_contactUpdate contactPUTUpdates a contact's details (only the fields sent change): name, phone, email, address, birthday, notes, tags, opt-out flags and custom field values. Returns the updated contact.

Custom field, 4 operations

list_contact_custom_fieldsList contact custom fieldsGETReturns a contact's custom field values, each as the custom field id and its value.
list_custom_fieldsList custom fieldsGETLists the account's contact custom field definitions: id, label, code, type (string, number, date or boolean) and order.
update_contact_custom_fieldUpdate contact custom fieldPUTSets one custom field value on a contact. The value is a string read according to the field's type (string, number, date or boolean); an empty value clears the field.
update_custom_fieldUpdate custom fieldPUTRenames a contact custom field definition.

Media, 4 operations

add_campaign_event_mediaAdd campaign event mediaPOSTAdds one image (jpg, jpeg, png or gif) to a campaign event, which holds at most 3 media files. The file comes from a previous step.
delete_campaign_event_mediaDelete campaign event mediaDELETERemoves every media file (image) from a campaign event, leaving its text.
delete_campaign_event_media_at_indexDelete campaign event media at indexDELETERemoves the media file at one position (0 to 2) from a campaign event.
replace_campaign_event_mediaReplace campaign event mediaPUTReplaces the image at one position (0 to 2) of a campaign event with a new file from a previous step (jpg, jpeg, png or gif).

Remove, 4 operations

remove_contact_from_campaignRemove contact from campaignPUTRemoves a contact from a campaign, so the contact receives no further messages from it.
remove_smart_list_contactsRemove smart list contactsPUTRemoves contacts from a Smart List by id. The contacts themselves are kept.
remove_smart_list_keywordsRemove smart list keywordsPUTUnlinks join keywords from a Smart List.
remove_tag_from_contactsRemove tag from contactsPUTRemoves a tag from several contacts and returns the tag with a count and a subset of the contacts still tagged.

Smart list, 4 operations

create_smart_listCreate smart listPOSTCreates an empty Smart List (a contact list) with a name unique to the account. Add contacts with add_smart_list_contacts or a query with set_smart_list_query.
delete_smart_listDelete smart listDELETEDeletes a Smart List. The contacts themselves are kept.
get_smart_listGet smart listGETReturns one Smart List: name, dates and its query state (query tree, contact count, last evaluation, error).
update_smart_listUpdate smart listPUTRenames a Smart List (the name is its only field this tool changes).

Trackable link, 4 operations

create_trackable_linkCreate trackable linkPOSTCreates a trackable link (a short link that records which contacts click it), optionally tagging contacts who click.
delete_trackable_linkDelete trackable linkDELETEDeletes a trackable link.
get_trackable_linkGet trackable linkGETReturns one trackable link: name, destination URL, slug and auto-tag.
update_trackable_linkUpdate trackable linkPUTUpdates a trackable link's name, destination URL and auto-tag setting.

Campaign, 3 operations

delete_campaignDelete campaignDELETEDeletes a campaign. Its contacts stop receiving the campaign's scheduled messages.
get_campaignGet campaignGETReturns one campaign's id, name and type.
update_campaignUpdate campaignPUTRenames a campaign (its name is the only field this tool changes).

User custom field, 3 operations

list_user_custom_fieldsList user custom fieldsGETLists the account-level custom fields (values the account reuses in messages): id, name and value.
update_user_custom_fieldUpdate user custom fieldPUTUpdates one account-level custom field's name and value.
update_user_custom_fieldsUpdate user custom fieldsPUTUpdates several account-level custom fields at once: an object keyed by field id, each with a new name and/or value.

Country, 2 operations

get_countryGet countryGETReturns one supported country's name and two-letter code.
list_countriesList countriesGETLists the countries Project Broadcast supports, each with its name and two-letter code.

Event, 2 operations

list_campaign_eventsList campaign eventsPOSTLists the events of a campaign: each scheduled message with its text, media and timing (a date, a delay or an offset from the contact's event date).
update_campaign_eventUpdate campaign eventPUTUpdates one campaign event: its name, message text and schedule. Send only the timing fields that match the campaign's type (drip, delay, event, countdown or repeat).

Opt out text, 2 operations

get_opt_out_textGet opt out textGETReturns the opt-out text the account appends to messages.
update_opt_out_textUpdate opt out textPUTChanges the opt-out text the account appends to messages.

Query, 2 operations

clear_smart_list_queryClear smart list queryDELETERemoves the query from a Smart List: its current members stay and the list becomes static.
set_smart_list_querySet smart list queryPUTSaves a query tree on a Smart List and evaluates it at once: matching contacts are added and the others removed. Check the tree first with preview_smart_list_query.

State, 2 operations

get_stateGet stateGETReturns one state or province of a supported country: its name and code.
list_statesList statesGETLists the states or provinces of a supported country, each with its name and code.

Apply, 1 operation

apply_keyword_to_contactApply keyword to contactPUTApplies a keyword to a contact. Keywords carry the automated responses configured in Project Broadcast, which may then text the contact and spend credits. Returns the contact.

Archive, 1 operation

archive_contactArchive contactPUTArchives a contact: it can no longer be messaged or emailed and its inbound messages are rejected. Opt-out flags are not changed.

Broadcast, 1 operation

create_broadcastCreate broadcastPOSTSends one message (text or a saved template, voicemail drops included) to a list of contacts, now or at scheduledAt. It texts real people's phones and spends credits per contact: 1 per text, 2 per voicemail drop.

Click, 1 operation

list_trackable_link_clicksList trackable link clicksPOSTLists the clicks on a trackable link by known contacts, page by page: the contact id and the time of each click.

Credit, 1 operation

get_creditsGet creditsGETReturns the number of message credits left on the account (a text costs 1 credit, a voicemail drop 2).

Double opt in, 1 operation

record_double_opt_inRecord double opt inPUTRecords that a contact gave double opt-in consent elsewhere (your own form): clears doNotMessage and texts the contact a consent confirmation, a message to a real person that can spend 1 credit. Already opted-in contacts are not texted.

Import, 1 operation

import_contactsImport contactsPOSTCreates or updates up to 100 contacts in one call; an item carrying contactId updates that contact. Returns one result per item, the contact or an error. Contact records are personal data.

Keytest, 1 operation

test_api_keyTest api keyGETChecks that the API key works and returns the Project Broadcast account it acts on: the account name and its texting phone number.

Landing page, 1 operation

get_landing_pageGet landing pageGETReturns one landing page: internal name, title, meta description, public URL and dates.

Preview, 1 operation

preview_smart_list_queryPreview smart list queryPOSTRuns a query tree against the account's contacts and returns the matching contacts page by page with their count, without saving anything. Contact records are personal data.

Require double opt in, 1 operation

get_double_opt_in_settingsGet double opt in settingsGETReturns whether the account requires double opt-in and whether it sends the automatic double opt-in message.

Schema, 1 operation

get_smart_list_query_schemaGet smart list query schemaGETReturns the fields and operators a Smart List query tree accepts, including the account's custom fields (customField:<id>). Use it before preview_smart_list_query or set_smart_list_query.

Send, 1 operation

send_message_to_contactSend message to contactPOSTSends a text message (or a saved template's content) to one contact, now or at runAt. It texts a real person's phone and can spend credits (1 per text; the vendor charges scheduled and automated messages).

Tag, 1 operation

delete_tagDelete tagDELETERemoves a tag from every contact that carries it.

Timezone, 1 operation

get_timezoneGet timezoneGETReturns the account's time zone name, used for dates sent without an offset.

Unarchive, 1 operation

unarchive_contactUnarchive contactPUTUnarchives a contact so it can be messaged again. An opt-out (doNotMessage and the other flags) set before archiving stays in effect.

View, 1 operation

list_landing_page_viewsList landing page viewsPOSTLists the views of a landing page by known contacts, page by page: the contact id and the time of each view.

Use Project Broadcast from Claude Code, Cursor or Codex

Connect Project Broadcast in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Project Broadcast operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Project Broadcast

Create your workspace
Sign up free. Nothing to install.
Connect Project Broadcast once
Add your Project Broadcast connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.