Integration

Attentive integration

Attentive SMS and email marketing through its v1 API. Subscribe and unsubscribe people, check what a person is subscribed to, write custom attributes onto them, and send the behavioural events that Attentive journeys react to, including the three e-commerce ones for product views, add to cart and purchase. There is no send-a-message call: messaging is triggered by the journeys that these events feed.

Connect Attentive How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Attentive use cases

feeding a cart abandonment journey
feeding a browse abandonment journey
honouring an opt out captured elsewhere
checking consent before sending a message
opting a customer in after a checkout consent box
verifying a credential before a campaign workflow
reading stored traits before personalising a message
stopping abandonment journeys once a customer converts
writing loyalty tier onto a subscriber for segmentation
triggering a win back journey when a customer goes quiet

What you can do with Attentive

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.

Ecommerce event, 3 operations

record_add_to_cartRecord add to cartPOSTSends an add to cart event for a person.
record_product_viewRecord product viewPOSTSends a product view event for a person.
record_purchaseRecord purchasePOSTSends a purchase event for a person.

Subscription, 3 operations

get_subscriptionsGet subscriptionsGETReturns the subscription eligibilities of one person.
subscribe_userSubscribe userPOSTCreates a subscription for a person and reports whether it was new.
unsubscribe_userUnsubscribe userPOSTOpts a person out and reports whether they already were.

Attribute, 2 operations

get_custom_attributesGet custom attributesGETReturns the custom attributes of one person as a plain array.
set_custom_attributesSet custom attributesPOSTStores custom attribute values for a person.

Account, 1 operation

get_meGet meGETReturns the company and application behind the credential.

Coupon, 1 operation

create_couponsCreate couponsPOSTAdds codes to a coupon pool for messages to hand out.

Event, 1 operation

send_custom_eventSend custom eventPOSTRecords a custom event that journeys can react to.

Use Attentive from Claude Code, Cursor or Codex

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

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

Attentive integration FAQ

What can you do with the Attentive integration?

LiveContext exposes 11 operations on Attentive, covering ecommerce event, subscription, attribute and account. Common uses include feeding a cart abandonment journey, feeding a browse abandonment journey and honouring an opt out captured elsewhere.