Integration

SendX integration

SendX is an email marketing platform. An agent can create, update, find, unsubscribe and delete contacts, upsert contacts by email (one or up to 25 at once), record custom and revenue events, send transactional emails directly or from a template, create campaigns and read their performance reports, and manage lists, tags, custom fields, senders, sending domains, email templates, webhooks, team members and blog posts with their categories and tags. Sending an email, or creating a campaign set to send immediately, delivers mail at once and cannot be undone. Authentication is the Team API key sent in the X-Team-ApiKey header (SendX settings, Team API Key).

Connect SendX How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with SendX

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.

Contact, 8 operations

create_contactCreate contactPOSTCreates a contact; the email must be unique within the team. Attach lists and tags by identifier and set custom fields. To create or update by email, use identify_contact.
delete_contactDelete contactDELETESoft-deletes a contact: it is removed from all lists and its pending campaigns are cancelled, while its history is kept.
get_contactGet contactGETReturns one contact: name, email, company, custom fields, lists, tags and delivery flags (unsubscribed, bounced, spam, blocked, dropped).
identify_contactIdentify contactPOSTCreates a contact, or updates the one with the same email: names, company, custom fields, tags and lists. Pass newEmail to change an existing contact's address.
identify_contacts_bulkIdentify contacts bulkPOSTCreates or updates up to 25 contacts in one call, matched by email, each with the same fields as identify_contact.
list_contactsList contactsGETLists contacts with their lists, tags and custom fields, 10 per page by default (at most 100). search matches first name, last name or email, case-insensitively.
unsubscribe_contactUnsubscribe contactPOSTUnsubscribes a contact from all marketing emails.
update_contactUpdate contactPUTUpdates a contact by identifier. email is required by the vendor schema; set the lists, tags and custom fields to apply.

Contact tag, 6 operations

create_tagCreate tagPOSTCreates a contact tag; the name must be unique within the team.
delete_tagDelete tagDELETEDeletes a contact tag.
get_tagGet tagGETReturns one contact tag.
list_tagsList tagsGETLists the team's contact tags, 10 per page by default.
track_contact_tagsTrack contact tagsPOSTAdds or removes tags on a contact identified by email, which can trigger tag-based automations. Legacy route kept by SendX; identify_contact also sets tags.
update_tagUpdate tagPUTRenames a contact tag.

Blog post, 5 operations

create_postCreate postPOSTCreates a blog post. Leave isPublished out (false) to keep it unpublished.
delete_postDelete postDELETESoft-deletes a blog post and removes it from listings.
get_postGet postGETReturns one blog post with its content and SEO metadata.
list_postsList postsGETLists blog posts, 10 per page by default.
update_postUpdate postPUTUpdates a blog post: titles, content, category, tags, slug, publication and SEO fields. name and postTitle are required.

Contact list, 5 operations

create_listCreate listPOSTCreates a contact list.
delete_listDelete listDELETEDeletes a contact list.
get_listGet listGETReturns one contact list.
list_listsList listsGETLists the team's contact lists, 10 per page by default (at most 500); search matches list names.
update_listUpdate listPUTRenames a contact list.

Custom field, 5 operations

create_custom_fieldCreate custom fieldPOSTCreates a custom contact field. type is 0 text (up to 255 characters), 1 number, 2 date (YYYY-MM-DD), 3 boolean or 4 phone number.
delete_custom_fieldDelete custom fieldDELETEDeletes a custom field definition; values already stored on contacts are preserved.
get_custom_fieldGet custom fieldGETReturns one custom field definition: name, type and description.
list_custom_fieldsList custom fieldsGETLists the team's custom contact fields, 10 per page by default; search matches field names case-insensitively.
update_custom_fieldUpdate custom fieldPUTUpdates a custom field's name, type and description.

Email template, 5 operations

create_email_templateCreate email templatePOSTCreates a reusable email template, usable with send_template_email.
delete_email_templateDelete email templateDELETEDeletes an email template.
get_email_templateGet email templateGETReturns one email template with its content.
list_email_templatesList email templatesGETLists email templates, 10 per page by default (at most 100); search matches template names case-insensitively.
update_email_templateUpdate email templatePUTUpdates an email template's name, content and editor type.

Post category, 5 operations

create_post_categoryCreate post categoryPOSTCreates a blog post category.
delete_post_categoryDelete post categoryDELETESoft-deletes a blog post category.
get_post_categoryGet post categoryGETReturns one blog post category.
list_post_categoriesList post categoriesGETLists the blog post categories.
update_post_categoryUpdate post categoryPUTRenames a blog post category.

Post tag, 5 operations

create_post_tagCreate post tagPOSTCreates a blog post tag.
delete_post_tagDelete post tagDELETESoft-deletes a blog post tag.
get_post_tagGet post tagGETReturns one blog post tag.
list_post_tagsList post tagsGETLists the blog post tags.
update_post_tagUpdate post tagPUTRenames a blog post tag.

Webhook, 5 operations

create_webhookCreate webhookPOSTCreates a webhook that SendX calls on the chosen events (opened, clicked, bounced, dropped, marked spam, unsubscribed, contact created).
delete_webhookDelete webhookDELETEDeletes a webhook; its URL stops receiving events.
get_webhookGet webhookGETReturns one webhook: its URL, whether it is enabled and which events it receives.
list_webhooksList webhooksGETLists the webhooks configured for the team and the events each one receives.
update_webhookUpdate webhookPUTUpdates a webhook's URL, enabled state and the events it receives (opened, clicked, bounced, dropped, marked spam, unsubscribed, contact created). url and enabled are required.

Campaign, 4 operations

create_campaignCreate campaignPOSTCreates an email campaign to the given lists, tags or segments. scheduleType 1 sends it immediately (cannot be undone); 0 schedules it for scheduleCondition and timeCondition.
delete_campaignDelete campaignDELETEDeletes a campaign.
get_campaignGet campaignGETReturns one campaign with its content (htmlCode, plainText, previewText), status, schedule and targeted lists, tags and segments.
list_campaignsList campaignsGETLists campaigns, 10 by default, newest pages via offset. Filter by campaignType. The list omits htmlCode, plainText and previewText: call get_campaign for those.

Sending domain, 4 operations

create_sending_domainCreate sending domainPOSTAdds a sending domain. It must then be verified by publishing the DKIM, SPF and DMARC records that get_sending_domain returns.
delete_sending_domainDelete sending domainDELETEDeletes a sending domain.
get_sending_domainGet sending domainGETReturns one sending domain with its verification status and the DNS records (DKIM, SPF, DMARC) to configure.
list_domainsList domainsGETLists the team's sending domains with verification status and DNS configuration, 10 per page by default.

Email, 2 operations

send_emailSend emailPOSTSends a transactional email now (cannot be undone). Answers 202 when queued: delivery happens later and per-recipient results are not returned.
send_template_emailSend template emailPOSTSends an email built from a saved template now (cannot be undone). Answers 202 when queued: delivery and personalization happen later, results are not returned.

Sender, 2 operations

create_senderCreate senderPOSTAdds a sender address (display name and email). The address must be verified before campaigns can use it.
list_sendersList sendersGETLists the team's sender addresses; their identifiers are what create_campaign takes as sender.

Team member, 2 operations

get_team_memberGet team memberGETReturns one SendX team member.
list_team_membersList team membersGETLists the members of the SendX team: email, user name, full name and avatar.

Campaign report, 1 operation

get_campaign_reportGet campaign reportGETReturns a campaign's performance report: sent, opened, clicked (total and unique), bounced, unsubscribed and spam counts, and clicks per link.

Custom event, 1 operation

track_custom_eventTrack custom eventPOSTRecords a custom event (for example video_watched) for a contact, with optional event data and time.

Revenue event, 1 operation

track_revenue_eventTrack revenue eventPOSTRecords a revenue event (an amount, its source and time) for a contact, for revenue attribution.

Use SendX from Claude Code, Cursor or Codex

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

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