What can you do with the Mailpit integration?

LiveContext exposes 23 operations on Mailpit, covering message, tag, chao and search.

Mailpit integration

Mailpit is a self-hosted SMTP test server that captures the mail an application sends so it can be inspected instead of delivered. This integration covers its v1 API: list, search and read captured messages with their headers, addresses, body and inline HTML, download the raw source or an attachment and its thumbnail, mark messages read or unread, tag them and rename or delete tags, delete messages one by one or by search query, release a captured message to real recipients through a configured SMTP relay, send a new message through Mailpit, run the built-in HTML compatibility, link and SpamAssassin checks on a message, read server information and the web UI configuration, and drive the Chaos failure-injection triggers. The host is part of the credential because every Mailpit install is its own deployment. Authentication is the optional HTTP basic auth Mailpit enforces when the instance is started with UI authentication.

23 toolsBasic authAPI docs

Connect Mailpit How integrations work

What you can do with Mailpit

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.

Message, 4 operations

DELETEdelete_messages
Delete messages.
GETget_message
Get message summary.
GETlist_messages
List messages.
PUTset_messages_read_status
Set read status.

Tag, 4 operations

DELETEdelete_tag
Delete a tag.
GETlist_tags
Get all current tags.
PUTrename_tag
Rename a tag.
PUTset_message_tags
Set message tags.

Chao, 2 operations

GETget_chaos_triggers
Get Chaos triggers.
PUTset_chaos_triggers
Set Chaos triggers.

Search, 2 operations

DELETEdelete_messages_by_search
Delete messages by search.
GETsearch_messages
Search messages.

Header, 1 operation

GETget_message_headers
Get message headers.

Html check, 1 operation

GETcheck_message_html
HTML check.

Info, 1 operation

GETget_server_info
Get application information.

Link check, 1 operation

GETcheck_message_links
Link check.

Part, 1 operation

GETdownload_message_attachment
Get message attachment.

Raw, 1 operation

GETdownload_message_source
Get message source.

Release, 1 operation

POSTrelease_message
Release message.

Sa check, 1 operation

GETcheck_message_spam_score
SpamAssassin check.

Send, 1 operation

POSTsend_message
Send a message.

Thumb, 1 operation

GETdownload_attachment_thumbnail
Get an attachment image thumbnail.

Webui, 1 operation

GETget_web_ui_config
Get web UI configuration.

Use Mailpit from Claude Code, Cursor or Codex

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

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