Integration

The Newsletter Plugin integration

The Newsletter Plugin is a WordPress newsletter and mailing list plugin. This integration covers its REST API v2: list, add, update, unsubscribe or delete subscribers and set their list memberships, status and extra profile fields, start the public subscription process (which can send an activation or welcome email), read the subscription lists and extra profile field definitions, and read the newsletters already sent. Subscriber reads return only the id, status and list memberships: email addresses, names, location, gender and extra profile field values are withheld. Every site is its own deployment, so the site URL is part of the connection; the free API addon must be installed. Authentication is a client key and client secret pair created under Newsletter, API in the WordPress admin, sent as the client_key and client_secret query parameters (the vendor's documented alternative to HTTP Basic auth); a read-only key can call only the read tools. The vendor documents no rate limit.

Connect The Newsletter Plugin How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with The Newsletter Plugin

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, 5 operations

create_subscriberCreate subscriberPOSTAdds a new subscriber with an email and optional profile, status and lists. Sends no activation or welcome email. Fails if the email already exists. Acts for real.
delete_subscriberDelete subscriberDELETEPermanently deletes a subscriber found by email or id, with all their data and statistics; cannot be undone. To stop sending but keep data, set status unsubscribed with update_subscriber.
get_subscriberGet subscriberGETGets one subscriber by email address or id. Returns only the subscriber id, status and list memberships; profile data is withheld.
list_subscribersList subscribersGETLists subscribers page by page (per_page up to 100, default 10). Each item gives only the subscriber id, status and list memberships; emails and names are withheld.
update_subscriberUpdate subscriberPUTChanges only the fields sent on a subscriber found by email or id, or creates the subscriber when the email is new (upsert). Acts for real: list changes can start Autoresponder emails.

Extrafield, 2 operations

get_extra_fieldGet extra fieldGETGets one extra profile field definition by its number (1 to 20): name, type, select options and whether it is required.
list_extra_fieldsList extra fieldsGETLists the extra profile fields configured on the site: number (1 to 20), name, type (text or select), the allowed options of a select field and whether it is required.

List, 2 operations

get_listGet listGETGets one subscription list by its number (1 to 40) and returns its name.
list_listsList listsGETLists every subscription list configured on the site (public and private) with its number (1 to 40) and name. Use the numbers in the lists param of subscriber tools.

Newsletter, 1 operation

list_newslettersList newslettersGETLists the newsletters already completely sent, the most recent first, 10 per page by default, with subject, HTML and plain text content and send date. Drafts, paused, scheduled or still sending ones are not returned.

Subscription, 1 operation

start_subscriptionStart subscriptionPOSTStarts the public subscription process for an email: spam and duplicate checks, then an activation or welcome email depending on the opt-in mode. Sends email for real.

Use The Newsletter Plugin from Claude Code, Cursor or Codex

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

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