Integration

Netcore Email API integration

Netcore Email API (V6, formerly Pepipost) sends transactional and marketing email from your verified sending domains. This integration can send email (with personalizations, attachments, templates, tags and scheduling), manage HTML templates, add, verify, allocate and delete sending domains, manage the global suppression list of email addresses and domains, read hourly-updated delivery statistics and per-message event logs, request a full log export, and manage subaccounts and their credits (list, enable or disable, delete, add or remove credits, recurring credits). Message logs omit recipient and sender addresses and the IP addresses and links of opens and clicks. Left out: webhook management (callback URLs and custom headers), API key management, dedicated IP and IP pool management, subaccount creation (it returns a new API key), the listing of suppressed email addresses, and the payload-encryption and gzip headers. Authentication is the Email API key from Settings, Integrations, API, sent as Authorization: Bearer; the connection also names the region host (EU or non-EU). A master account can act for a subaccount with the on-behalf-of param. The docs state no rate limit.

Connect Netcore Email API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Netcore Email API.Built from the 29 Netcore Email API tools below, on the connection you add once.

What you can do with Netcore Email API

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.

Domain, 7 operations

add_domainAdd domainPOSTAdds a sending domain to the account (with its envelope name and an optional inbound name). Then publish the DNS records shown by get_domain and run verify_domain_dns.
add_suppressed_domainsAdd suppressed domainsPOSTSuppresses whole domains: every address under them is blocked from future delivery. Acts for real.
delete_domainDelete domainDELETERemoves a sending domain from the account (or the named subaccount); it can no longer be used to send. Acts for real.
get_domainGet domainGETGets a sending domain's DNS records to publish (DKIM, custom envelope and inbound), each with its host, required value, current value and whether it is valid, plus the domain status and tracking settings.
get_suppressed_domainGet suppressed domainGETChecks whether one domain is on the suppression list, with when it was added and last changed and its status code.
list_suppressed_domainsList suppressed domainsGETLists the suppressed domains with when each was added and its status code. Page with offset and limit (default 1000).
remove_suppressed_domainsRemove suppressed domainsDELETERemoves domains from the suppression list so their addresses can receive email again. Acts for real.

Template, 5 operations

create_templateCreate templatePOSTCreates a stored email template from a name and HTML content (only the first html block is kept). Returns its id for send_email template_id.
delete_templateDelete templateDELETEPermanently deletes a stored template; it cannot be recovered.
get_templateGet templateGETGets one stored template by id: name and creation and update dates.
list_templatesList templatesGETLists stored email templates with id, name and creation and update dates. Page with limit (at most 1000) and offset.
update_templateUpdate templatePATCHReplaces a template's name and HTML content (both required; only the first content block is used). Changes the stored template for real.

Email, 3 operations

add_suppressed_emailsAdd suppressed emailsPOSTSuppresses email addresses: every future delivery to them from the account is blocked. Acts for real.
get_email_suppression_statusGet email suppression statusGETChecks whether one email address is on the suppression list, with when it was added and its status code.
remove_suppressed_emailsRemove suppressed emailsDELETERemoves email addresses from the suppression list so they can receive email again. Acts for real.

Subaccount, 3 operations

delete_subaccountDelete subaccountDELETEDeletes a subaccount for real.
list_subaccountsList subaccountsGETLists subaccounts with username, whether they are disabled and their credit type and credits. Filter by username; page with limit (default 10, max 1000) and offset.
update_subaccountUpdate subaccountPATCHEnables or disables a subaccount (a disabled subaccount cannot send). Acts for real.

Download, 2 operations

get_log_export_statusGet log export statusGETGets the status of a log export started with request_log_export (for example Completed), with request and completion dates. The file itself is delivered by email or SFTP.
request_log_exportRequest log exportPOSTStarts a real export of the email transaction logs for a period of at most 31 days; the file link is sent to the account's registered email or to an SFTP connection. Returns a request id for get_log_export_status.

Addrecurringcredit, 1 operation

set_subaccount_recurring_creditSet subaccount recurring creditPOSTSets, or enables or disables, a recurring credit top-up for a subaccount (daily, weekly or monthly between two dates). Acts for real.

Allocate, 1 operation

allocate_domain_to_subaccountAllocate domain to subaccountPOSTAssigns an existing, unallocated domain to one subaccount (a domain belongs to one subaccount at a time). Acts for real.

Credit, 1 operation

get_subaccount_creditsGet subaccount creditsGETGets a subaccount's credit type, assigned credits, balance and recurring credit schedule.

Message, 1 operation

list_message_logsList message logsGETLists per-message event logs for a period (start_date and event_start_date required; the event window may span at most 31 days), 50 by default and up to 1000 per call; pass the returned scrollId as scrollid for the next page.

Modify, 1 operation

modify_subaccount_creditsModify subaccount creditsPOSTAdds credits to or removes credits from a subaccount's balance. Changes its sending allowance for real.

Profile, 1 operation

update_profile_timezoneUpdate profile timezonePATCHChanges the account's timezone (IANA name such as America/New_York), which sets how stats dates are computed. Changes the setting for real.

Send, 1 operation

send_emailSend emailPOSTSends a real email now (or at send_at) from a verified domain to the recipients in personalizations. Uses your account's email credits. Returns the message_id for list_message_logs.

Stats, 1 operation

get_statsGet statsGETGets delivery statistics (processed, sent, opens, clicks, bounces, spam, unsubscribes and more) for a date range, grouped by day, week, month, tag, domain, sender or subaccount. Updated hourly.

Validate, 1 operation

verify_domain_dnsVerify domain dnsGETChecks a domain's DNS setup now (DKIM, envelope sender and the other records) and returns, per record, whether it is valid with the required and current values.

Use Netcore Email API from Claude Code, Cursor or Codex

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

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