Integration

Sendr integration

Sendr is a sales outreach platform that builds personalized landing pages (with dynamic audio, GIF and LipSync video assets), contact sheets and outreach campaigns. Generate a personalized page from a page template and read its rendering status and asset URLs, list templates and their variables, list sheets and their columns and add contact rows, list and read campaigns, and manage workspace webhooks. Generating a page spends Sendr credits. The raw sheet object (undocumented fields), the webhook secret reveal route, the older personalized-page route and the webhook receiver documented for your own server are not exposed. Authentication is a workspace API key from Settings, API, sent in the X-API-Key header (a Bearer header is refused).

Connect Sendr How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Sendr.Built from the 15 Sendr tools below, on the connection you add once.

What you can do with Sendr

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.

Webhook, 4 operations

create_webhookCreate webhookPOSTCreate a workspace webhook: Sendr will POST the chosen events (page renders, page engagement, templates, sheets) to the url. Deliveries carry a secret in X-Webhook-Secret, shown in Sendr Settings, Webhooks, not here.
delete_webhookDelete webhookDELETEDelete a workspace webhook for good: Sendr stops sending it events. Identify it by url (required by the vendor) and id from list_webhooks.
list_webhooksList webhooksGETList the workspace webhooks: id, name, destination url, subscribed events, enabled flag, failure count and last failure reason, attributes and dates. The signing secret is not returned (it is shown in Sendr Settings, Webhooks).
update_webhookUpdate webhookPATCHUpdate a workspace webhook's url, events or attributes. Send url (required by the vendor) and id from list_webhooks. The vendor does not document whether fields left out are kept, so send the full events list.

Campaign, 2 operations

get_campaignGet campaignGETGet one outreach campaign: name, status, number of sequence steps and contacts, primary sheet id, owner and workspace ids, creator and last editor (names and emails of workspace members).
list_campaignsList campaignsGETList the outreach campaigns of the workspace, paged, with id, name, status, step and contact counts, primary sheet and creator. Filter by status or a search term.

Column, 1 operation

list_sheet_columnsList sheet columnsGETList the columns of a sheet: name, data type and format, select options, display order, linked contact property and enrichment. Call it before add_sheet_row to learn the sheet's columns.

Enabling, 1 operation

set_webhook_enabledSet webhook enabledPOSTTurn a workspace webhook on or off: enabled=true resumes deliveries (also the way back after Sendr disabled it for failures), enabled=false pauses them. Identify it by url and id from list_webhooks.

List, 1 operation

list_page_templatesList page templatesGETList the page templates of the workspace. A template id is what generate_page (templateId) and get_page_template_variables take.

Me, 1 operation

get_current_userGet current userGETGet the Sendr user (seat) and workspace the API key belongs to: workspace id and name, seat id, role, and the user's email and name (personal data). Use it to check that the key works.

Page, 1 operation

get_pageGet pageGETGet a generated page: its URL, rendering status (eventStatus pending, done or failed), the generated asset URLs (GIF, audio, LipSync video), processing flags, the contact and variables used, and any error message.

Row, 1 operation

add_sheet_rowAdd sheet rowPOSTAdd one row (one contact) to a sheet and return the new row id and number. A sheet can be a campaign's contact list (list_sheets shows campaignId); what a live campaign does with a new contact is set in that campaign.

Sendr page, 1 operation

generate_pageGenerate pagePOSTGenerate a personalized page from a page template; spends Sendr credits (1 per page, plus 1 for a dynamic video background or audio). Returns pageId and pageUrl at once; poll get_page until eventStatus is done or failed.

Sheet, 1 operation

list_sheetsList sheetsGETList the sheets (contact lists) of the workspace with their id, name, row count, owner name and linked campaign. Use a sheet id with list_sheet_columns or add_sheet_row.

Variable, 1 operation

get_page_template_variablesGet page template variablesGETList the variables of a page template: each tag (the key to use in generate_page variablesValues), its label, example value and fallback.

Use Sendr from Claude Code, Cursor or Codex

Connect Sendr in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Sendr 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 Sendr

Create your workspace
Sign up free. Nothing to install.
Connect Sendr once
Add your Sendr 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.