Inspect SendPost delivery statistics, sending IPs, message metadata, domains, and suppressions. For SendPost customers reviewing email delivery and sending infrastructure. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"sendpost": {
"url": "https://sendpost.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"sendpost": {
"type": "http",
"url": "https://sendpost.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Use an account key to read daily or aggregate delivery, bounce and engagement counts across sub-accounts over a date range.
sendpost_list_account_stats sendpost_get_account_stats
Use an account key to inspect sending IP warmup states and IP pool routing or overflow settings without changing them.
sendpost_list_ips sendpost_list_ip_pools
Use a sub-account key to inspect domain DNS records, verification status and failure reasons without creating or verifying domains.
sendpost_list_domains sendpost_get_domain
Use a sub-account key to review suppressed recipients and their reasons over a date range. This does not add or remove suppressions.
sendpost_list_suppressions
Use an account key to look up a submitted message’s sender, recipient, subject and routing metadata. Results exclude message bodies, attachments and custom headers.
sendpost_get_message_metadata
The login page asks for your API key type and SendPost API key.
Find your API keys in your SendPost dashboard. Choose Account for sub-account statistics, message metadata, IPs and IP pools; choose Sub-account for domain and suppression audits. Paste the matching key, not SMTP credentials. Only tools for that key type can run. SendPost service access is purchased separately; existing customers can use their own keys. Connecting performs one small read to validate the key and does not send email or alter your account.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API key type and SendPost API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the SendPost connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
sendpost_list_subaccounts | read | List SendPost sub-accounts READ (account key): List sub-accounts and safe account metadata. API keys and SMTP credentials are never returned. |
sendpost_get_subaccount | read | Get SendPost sub-account READ (account key): Get a sub-account's safe metadata, labels and blocked state. Credentials are excluded. |
sendpost_list_ips | read | List SendPost sending IPs READ (account key): List sending IPs, warmup and state metadata. Does not allocate or change IPs. |
sendpost_get_ip | read | Get SendPost sending IP READ (account key): Inspect an existing sending IP's public address, reverse DNS and warmup state. |
sendpost_list_ip_pools | read | List SendPost IP pools READ (account key): List IP pool names, routing strategy, overflow settings and safe public IP metadata. |
sendpost_get_ip_pool | read | Get SendPost IP pool READ (account key): Inspect one IP pool's routing strategy, overflow settings and public IP metadata. Provider credentials and routing internals are excluded. |
sendpost_list_account_stats | read | List SendPost account daily statistics READ (account key): Daily delivery, bounce, open, click, unsubscribe and spam counts across sub-accounts. Use up to 366 days per call. |
sendpost_get_account_stats | read | Get SendPost account aggregate statistics READ (account key): Aggregate delivery and engagement counts across sub-accounts over a date range, up to 366 days. |
sendpost_get_account_group_stats | read | Get SendPost account group statistics READ (account key): Aggregate delivery and engagement counts for an existing group/tag across sub-accounts, up to 366 days. |
sendpost_list_subaccount_stats | read | List SendPost sub-account statistics READ (account key): Read a sub-account's delivery and engagement statistic records for a date range, up to 366 days. |
sendpost_get_subaccount_stats | read | Get SendPost sub-account aggregate statistics READ (account key): Aggregate delivery and engagement counts for one sub-account over a date range, up to 366 days. |
sendpost_get_message_metadata | read | Get SendPost message metadata READ (account key): Inspect a submitted message's ID, sender, recipient, subject, groups and routing metadata. Excludes bodies, attachments, custom headers and recipient custom fields. Large messages may exceed the 1 MiB read limit. |
sendpost_list_domains | read | List SendPost sending domains READ (sub-account key): Audit sending domains, DNS record configuration and verification failures. Does not create or verify domains. |
sendpost_get_domain | read | Get SendPost sending domain READ (sub-account key): Inspect a sending domain's DNS records and verification status. |
sendpost_list_suppressions | read | List SendPost suppressed recipients READ (sub-account key): Inspect suppressions and documented reasons within a date range, with pagination. Does not add or remove suppressions. |
sendpost_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
sendpost_request_feature | Request a missing feature Tell usefulapi that the user needs something the SendPost tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
sendpost_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on SendPost (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
sendpost_cancel_subscription | Cancel the Pro subscription Cancel the caller's SendPost Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run sendpost_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this SendPost server only. Subscribe with sendpost_upgrade (it returns a Stripe Checkout link). Cancel any time with sendpost_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running sendpost_upgrade before then undoes the cancel. Or write to [email protected].
Compare delivery statistics. Inspect sending IPs and pools. Audit sending-domain configuration. Review suppressed recipients. Inspect message metadata. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by SendPost. The server calls the SendPost API with your own SendPost access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your API key type and SendPost API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API key type and SendPost API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the SendPost API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in SendPost.
All 15 SendPost tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this SendPost server only. Cancel any time: Pro then runs to the end of the paid period. Run sendpost_usage_status to see how many calls you used.
Ask the AI to run sendpost_upgrade: it returns a Stripe Checkout link. To cancel, run sendpost_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with sendpost_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.