Integration

Postmaster+ integration

Postmaster+ monitors email deliverability and compliance for the sending domains a team tracks. List and read domains with their SPF, DKIM, DMARC, MX and BIMI configuration, compliance verdicts per mail stream and blocklist status, read a domain's activity feed, read Comcast/Xfinity APRF feedback reports and a domain's APRF DNS status, set the APRF sender defined identifier, list Gmail Postmaster spam (feedback loop) identifiers with their complaint rates, check URLs, domains or IPs against blocklists, and take screenshots of a URL or HTML (both spend credits). Left out: the IP monitoring routes (they return sending IP addresses and their network location), the single-email intelligence routes (personal data lookups and postal append), and the seedbox routes, for which the vendor documents no response. Authentication is a team API token from Team Settings, API Tokens, sent as a Bearer token.

Connect Postmaster+How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Postmaster+.Built from the 14 Postmaster+ tools below, on the connection you add once.

What you can do with Postmaster+

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.

Aprf report, 2 operations

get_aprf_reportGet aprf reportGETRead one APRF report with its unsegmented metrics. A report of another team, one that could not be charged and an unknown id all answer 404.
list_aprf_reportsList aprf reportsGETList the Comcast/Xfinity APRF (aggregate postmaster report feedback) reports the team received, with source, DKIM selector, dates and approximate metric buckets. Defaults to the last 90 days.

Domain, 2 operations

get_domainGet domainGETRead one tracked domain: its SPF, DKIM, DMARC, MX and BIMI configuration, alignment, settings, pre-send and post-send compliance verdicts per mail stream, complaint rate averages and blocklist status.
list_domainsList domainsGETList the sending domains the team tracks in Postmaster+, with their id, name and description, paginated. Pass an id to get_domain, list_domain_feed or get_domain_aprf_status.

Screenshot, 2 operations

get_screenshotGet screenshotGETRead one screenshot: its image URL, format, size, device scale, credits used and capture times.
list_screenshotsList screenshotsGETList the team's screenshots with their image URL, format, size and credits used, newest first by default, paginated.

Spam identifier, 2 operations

get_spam_identifierGet spam identifierGETRead the daily Gmail complaint rate time series of one spam (feedback loop) identifier, per domain, with the average over the selected date range.
list_spam_identifiersList spam identifiersGETList the Gmail Postmaster Tools v2 spam (feedback loop) identifiers reported for the team's domains in a date range, with sample count and average, minimum and maximum complaint rate.

Aprf sdi, 1 operation

update_domain_aprf_sdiUpdate domain aprf sdiPUTSet or clear the APRF sender defined identifier (SDI) pair of a domain owned by the team. This changes the DNS records the domain owner must publish: records published before no longer match the recommendation.

Aprf status, 1 operation

get_domain_aprf_statusGet domain aprf statusGETRead the stored APRF DNS and consent snapshot of a domain (wildcard and per-selector records, validity, SDI pair) and the DNS records to publish to receive reports. A snapshot, not a live lookup: see checked_at.

Feed, 1 operation

list_domain_feedList domain feedGETList a domain's activity feed (seed messages received and compliance events such as SPF is valid), paginated. Only available for activated domains (403 otherwise).

Start, 1 operation

start_blocklist_scanStart blocklist scanPOSTCheck up to 100 URLs, bare domains or public IPs against blocklists. Spends credits. The answer carries the status, counts and per-host results. Waits for the job and returns the finished result; gives up after 10 minutes.

Status, 1 operation

get_blocklist_scanGet blocklist scanGETRead a blocklist check started with start_blocklist_scan: status (pending, processing, completed, partially_completed, failed), counts, credits used and, once completed, per-host results.

Take, 1 operation

take_screenshotTake screenshotPOSTTake a screenshot of a web page URL or of HTML content and return the hosted image URL. Spends credits. Send url or html.

Use Postmaster+ from Claude Code, Cursor or Codex

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

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