Integration

Postscript integration

Postscript SMS marketing through its v2 API. The public surface is deliberately small and subscriber centred: list, read, create and update subscribers with their tags and custom properties, honour opt outs and erasure requests through the compliance endpoints, and send the behavioural events that Postscript automations react to. There is no message send, no campaign and no shop resource in this API. A credential is either a shop key or a partner key: a partner key acts on behalf of a shop only when the call also carries that shop's own private key in the X-Postscript-Shop-Token header, and without it a partner key is refused on every one of these operations.

Connect Postscript How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Postscript use cases

exporting the SMS list
tagging buyers after a purchase
honouring a data erasure request
triggering a back in stock message
honouring an opt out captured elsewhere
registering a subscriber captured on your own form
checking whether a subscriber can still be messaged
migrating an SMS list into Postscript
suppressing a customer after a complaint
reading the properties stored on a subscriber

What you can do with Postscript

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.

Subscriber, 4 operations

create_subscriberCreate subscriberPOSTCreates a subscriber from a phone number and returns the stored record.
get_subscriberGet subscriberGETReturns a single subscriber as a bare object.
list_subscribersList subscribersGETReturns a page of subscribers with page_info beside them.
update_subscriberUpdate subscriberPATCHApplies a partial update to a subscriber and returns the stored record.

Compliance, 2 operations

redact_subscriberRedact subscriberPATCHRequests erasure of a person and answers with a short acknowledgement.
unsubscribe_subscriberUnsubscribe subscriberPATCHUnsubscribes a person and answers with a short acknowledgement.

Event, 1 operation

create_eventCreate eventPOSTRecords an event that Postscript automations can react to and returns its identifiers.

Use Postscript from Claude Code, Cursor or Codex

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

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

Postscript integration FAQ

What can you do with the Postscript integration?

LiveContext exposes 7 operations on Postscript, covering subscriber, compliance and event. Common uses include exporting the SMS list, tagging buyers after a purchase and honouring a data erasure request.