Integration

Campaign Cleaner integration

Campaign Cleaner checks and fixes email campaign HTML before you send it. Submit a campaign to have it sanitized, CSS inlined and spam triggers corrected, then read the cleaned HTML and its analysis (spam keywords, text ratios, broken and blacklisted links, oversized images) or a PDF report; run inbox placement tests against seed mailboxes; and use the Inbox Placement Monitor to track where your real sends land per provider, with domains, messages, summaries and alert rules. Downloading a monitored message's raw original is not exposed. Authentication is an API key from API Management in your Campaign Cleaner account, sent in the X-CC-API-Key header; a submitted campaign and an inbox test cost 1 credit each, Monitor calls cost none (60 calls a minute per account).

Connect Campaign Cleaner How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Campaign Cleaner.Built from the 21 Campaign Cleaner tools below, on the connection you add once.

What you can do with Campaign Cleaner

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.

Campaign, 6 operations

delete_campaignDelete campaignPOSTPermanently deletes a saved campaign and its analysis. This cannot be undone. Answers status success, or error campaign not found when the id is not on your account.
get_campaignGet campaignPOSTReturns a completed campaign: the cleaned HTML, the settings applied, and the analysis (spam keywords, ratios, broken and blacklisted links, oversized images, change summary). Check get_campaign_status first.
get_campaign_pdf_reportGet campaign pdf reportPOSTReturns the analysis report of a saved campaign as a PDF file, stored as a file.
get_campaign_statusGet campaign statusPOSTReturns the processing status of a submitted campaign: processing, completed or paused. Once completed, call get_campaign for the cleaned HTML and the analysis.
list_campaignsList campaignsGETLists every campaign saved in your Campaign Cleaner account with its id, name, status (processing, completed or paused) and date added.
submit_campaignSubmit campaignPOSTSubmits email campaign HTML to be cleaned and analyzed (1 credit). Returns campaign.id at once; poll get_campaign_status until completed (usually seconds, up to about 2 minutes), then call get_campaign.

Monitor domain, 4 operations

add_monitor_domainAdd monitor domainPOSTAdds a sending domain to Inbox Placement Monitor and returns the DNS TXT record to publish; then call verify_monitor_domain. Freemail and shared sending domains are refused. Limit 20 an hour.
list_monitor_domainsList monitor domainsGETLists the sending domains on your Inbox Placement Monitor account, their verification status and DNS record to publish, and your domain limits. Only mail sent from a verified domain is recorded.
remove_monitor_domainRemove monitor domainPOSTRemoves a domain from Inbox Placement Monitor. Its stored messages and alerts are deleted at once and cannot be recovered.
verify_monitor_domainVerify monitor domainPOSTChecks the DNS TXT record of a pending domain. If verified is false the record was not found yet (DNS can take a while); try again later. Limit 30 attempts an hour.

Monitor alert, 3 operations

delete_monitor_alertDelete monitor alertPOSTDeletes a monitor alert rule and its alert history.
list_monitor_alertsList monitor alertsGETLists your monitor alert rules and the 50 most recent alerts. Each problem is reported once per domain and provider and resolves when mail lands in the inbox again.
save_monitor_alertSave monitor alertPOSTCreates a monitor alert rule, or replaces an existing one when alert_id is given. Recipients must be the account owner, team members, or addresses at a verified domain.

Inbox test, 2 operations

create_inbox_testCreate inbox testPOSTCreates an inbox placement test (1 credit; needs a Campaign Cleaner or Inbox Placement Tester subscription). Send your campaign to every send_to address, then call get_inbox_test_results with job_id.
get_inbox_test_resultsGet inbox test resultsPOSTReturns the placement results of an inbox test: summary rates and, per seed mailbox, whether it arrived and in which folder. Call again until status is Completed; it stays Processing while seeds have not received it.

Monitor message, 2 operations

get_monitor_messageGet monitor messageGETReturns one stored monitor message: placement, folder, authentication details with DKIM domain, sender IP, selected headers and a 300-character text preview.
list_monitor_messagesList monitor messagesGETLists stored copies of your mail that reached a monitor seed, newest first, with placement, folder and SPF/DKIM/DMARC results. Kept 30 days. Pass message_id to get_monitor_message for details.

Credit, 1 operation

get_creditsGet creditsGETReturns how many API credits your account has left. submit_campaign and create_inbox_test use 1 credit each; Inbox Placement Monitor tools use none.

Monitor seed, 1 operation

list_monitor_seedsList monitor seedsGETLists the Inbox Placement Monitor seed addresses. Add them as regular To recipients of your normal sends from a verified domain, and each copy is recorded with the folder it landed in. No credits used.

Monitor summary, 1 operation

get_monitor_summaryGet monitor summaryGETReturns the monitor inbox and spam rates overall and per provider. inbox_rate counts Gmail tabs (Promotions, Updates) as inbox. Rates are null when there is no mail.

Monitor usage, 1 operation

get_monitor_usageGet monitor usageGETReturns how many monitor messages were stored this billing period against your limits (null means unlimited), copies not stored after a limit, and when the counters reset.

Use Campaign Cleaner from Claude Code, Cursor or Codex

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

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