Skip to main content
Glama
Postmark Account MCP

Postmark Account MCP

by ckaklamanos

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
POSTMARK_ACCOUNTS_FILENoPath to the accounts file, which contains a JSON map of account names to Postmark Account API tokens, e.g. { "name": "token", ... } (or { "accounts": { ... } }). Kept outside the repo; permissions should be 600.~/.config/postmark-account-mcp/accounts.json
POSTMARK_ACCOUNT_TOKENNoAccount API token used as a fallback single account (named "default") if no accounts file exists.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_serversA

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

search_messagesA

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

get_message_detailsB

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

search_bouncesB

Search bounces across all servers (or one).

list_suppressionsA

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

delivery_statsB

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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