Skip to main content
Glama
Postmark Account MCP

Postmark Account MCP

by ckaklamanos

postmark-account-mcp

Read-only MCP server for Postmark that works across all servers of one or more Postmark accounts.

  • Auth with Account API tokens; each server's token is discovered automatically (GET /servers).

  • New servers / accounts appear without reconfiguration (5-min cache, accounts file re-read on refresh).

  • No send / create / update / delete operations exist — on purpose.

Tools

Every tool takes optional account and server (partial, case-insensitive; server also accepts a numeric ID or account/server). Omit them to query everything.

Tool

What

list_servers

All accounts → servers → message streams (tokens never returned)

search_messages

Outbound search (recipient, sender, subject, tag, status, stream, dates)

get_message_details

Event timeline of one message (Delivered / Bounced / Opened / Clicked); finds its server automatically

search_bounces

Bounces (email, type, inactive, dates)

list_suppressions

Suppressed recipients per stream

delivery_stats

Sent / bounce rate / spam / opens / clicks

Related MCP server: OpenArchiver MCP Server

Install (on any machine)

git clone https://github.com/ckaklamanos/postmark-account-mcp.git ~/Applications/postmark-account-mcp
cd ~/Applications/postmark-account-mcp && npm install

# accounts file — kept OUTSIDE the repo
mkdir -p ~/.config/postmark-account-mcp
cp accounts.example.json ~/.config/postmark-account-mcp/accounts.json
chmod 600 ~/.config/postmark-account-mcp/accounts.json
# edit it: { "account-name": "account-api-token", ... }

# register in Claude Code for ALL projects
claude mcp add --scope user postmark -- node ~/Applications/postmark-account-mcp/index.js

Account API token: Postmark → Account → API Tokens (not a server token).

Configuration

Variable

Default

POSTMARK_ACCOUNTS_FILE

~/.config/postmark-account-mcp/accounts.json

POSTMARK_ACCOUNT_TOKEN

Fallback single account (default) if no accounts file exists

Accounts file format: { "name": "token", ... } (or { "accounts": { ... } }).

Update

cd ~/Applications/postmark-account-mcp && git pull && npm install

Then restart Claude Code.

Requires Node 18+.

License

MIT

Available Tools

6 tools
delivery_statsDelivery statsB
Read-onlyIdempotent

Outbound overview per server: sent, bounced, bounce rate, spam complaints, opens, clicks.

Inputs: tag, server, stream, todate, +2 more.

get_message_detailsMessage delivery timelineB
Read-onlyIdempotent

Full details + event timeline (Delivered, Bounced, Opened, Clicked, ...) of one outbound message. If server is omitted, all servers are tried.

Inputs: message_id (required), server, account, include_body.

list_serversList Postmark accounts & serversA
Read-onlyIdempotent

List all configured accounts and their servers (name, ID, message streams). Tokens are never returned. Re-reads the accounts file.

Inputs: account, include_streams.

list_suppressionsList suppressionsA
Read-onlyIdempotent

Suppressed recipients per server/stream (hard bounces, spam complaints, manual). Omit server for all servers; omit stream for all streams.

Inputs: email, server, stream, account.

search_bouncesSearch bouncesB
Read-onlyIdempotent

Search bounces across all servers (or one).

Inputs: type, count, email, server, +4 more.

search_messagesSearch outbound messagesA
Read-onlyIdempotent

Search outbound messages across all servers (or one). Returns ID, status, recipients, subject, time. Use get_message_details for the delivery event timeline.

Inputs: tag, count, offset, server, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct concept: server inventory, message search, single-message drill-down, bounce search, suppression lists, and aggregate stats. The descriptions explicitly route between search_messages and get_message_details, though search_bounces vs list_suppressions could be momentarily confused since both relate to failed delivery and the distinction (events vs suppressed addresses) must be inferred.

    Naming Consistency4/5

    Five of six tools follow a clean verb_noun snake_case pattern (list_servers, search_messages, get_message_details, search_bounces, list_suppressions). delivery_stats breaks the pattern as a bare noun phrase, a minor deviation that is still readable in context.

    Tool Count5/5

    Six tools is well within the sweet spot for a focused read-only account/message observability server. Each tool covers a distinct facet (inventory, search, detail, bounces, suppressions, stats) with no filler.

    Completeness4/5

    The surface covers the core read workflows end-to-end: find servers, search and drill into messages, inspect bounces and suppressions, and roll up stats. Gaps exist but are minor for a read-only account server — no inbound message search, no way to fetch a single bounce or suppression record, and no suppression management (e.g. reactivating an address).

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only, provider-agnostic email access over IMAP, allowing users to list folders, search and read messages, and download attachments without ever marking messages as read.
      6
      30 PyPI
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides read-only search and retrieval of archived emails, archive statistics, health, and ingestion sources, with an optional administrative toolset for user, role, reindexing, and queue management.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Proton Mail through the local Proton Bridge, enabling search, retrieval, and listing of messages, threads, folders, and attachments without any mutating capabilities.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Klaviyo marketing data, including campaigns, flows, segments, metrics, reports, and customer profiles, across multiple Klaviyo accounts.
      24
      34 npm
      MIT