Run your email infrastructure from your agent.

Connect your MCP client to PostShiba. Look up recipients, read delivery, and pause a tenant without opening the dashboard.

Start free trial Connect MCP
Your agent Support key · 5 tools Support key · 5 tools Full access · 109 tools

Is Gmail having trouble with our mail today?

Thought for 2s

Check whether sending is held, then compare mailbox providers.

get_status nothing held
get_analytics dimension=mx_provider 3 providers

Gmail is deferring more than usual over the last 24 hours. Nothing is held or suspended on your side.

ProviderDeliveredDeferred
gmail.com 89.4% 8.4%
outlook.com 98.2% 1.2%
yahoo.com 97.9% 1.5%

Did alex@example.com get the password reset?

Thought for 1s

Look up the address and read its latest send.

lookup_recipient email=alex@example.com can_receive

Yes. The last send to alex@example.com was delivered at 09:14. The address is not suppressed.

alex@example.com Delivered Not suppressed 09:14

Acme is sending spam. Pause them while we look into it.

Thought for 2s

Suspend the acme tenant only. Every other tenant keeps sending.

Run suspend_tenant?

tenant=acme

Approved
suspend_tenant tenant=acme suspended

Acme is paused. Every other tenant is still sending. Ask me to resume them when you are ready.

Connect in three steps.

Paste one config block into your MCP client. The key you choose decides which tools your agent can call.

Read the API reference
Create API key

Name

Help desk

Access

Full access All 109 tools, for setup.
Support 5 tools, for the help desk.

Bearer token

YOUR_API_KEY Copy
~/.cursor/mcp.json
Cursor
1{ 2 "mcpServers": { 3 "postshiba": { 4 "url": "https://app.postshiba.com/mcp", 5 "headers": { 6 "Authorization": "Bearer YOUR_API_KEY" 7 } 8 } 9 } 10}
Your agent
Support key
postshiba Connected 5 tools
  • lookup_recipient
  • get_analytics
  • get_status
  • destroy_suppression
  • whoami
Did alex@example.com get the password reset?

Deploy, operate, and answer.

Every tool is a documented REST endpoint with the same KYC, payment, and send gates as the dashboard.

Stand up sending.

Create a shared-IP cluster, verify a sending domain, and issue SMTP credentials.

Tool calls
Full access
  1. create_cluster name=production POST /v1/clusters created
  2. get_cluster production GET /v1/clusters/:id sending_ready
  3. verify_sending_domain mail.acme.com POST /v1/sending_domains/:id/verify verified
  4. create_smtp_credential production POST /v1/clusters/:cluster_id/smtp_credentials issued

Contain one customer.

Pause a tenant or one sending domain while you investigate. Everyone else keeps sending.

Tool calls
Full access
  1. suspend_tenant acme POST /v1/tenants/:id/suspend suspended
  2. suspend_sending_domain mail.acme.com POST /v1/sending_domains/:id/suspend suspended
  3. create_suppression user@example.com POST /v1/suppressions suppressed
  4. resume_tenant acme POST /v1/tenants/:id/resume sending

Answer support questions.

Read delivery by mailbox provider, look up one recipient, and clear a suppression. A Support key is enough.

Tool calls
Support key
  1. get_status GET /v1/status nothing held
  2. get_analytics dimension=mx_provider GET /v1/analytics 3 providers
  3. lookup_recipient alex@example.com GET /v1/recipients delivered
  4. destroy_suppression sam@example.com DELETE /v1/suppressions/:id removed

Give support answers, not production access.

Full access keys set up the account. Support keys research delivery and cannot reconfigure it.

Same agent. Different key.

A Support key gets 5 tools for the help desk. No SMTP passwords, webhook secrets, DKIM private keys, or raw bounce payloads.

Tool calls
  1. whoami GET /v1/users/me allowed allowed
  2. lookup_recipient alex@example.com GET /v1/recipients allowed allowed
  3. get_analytics dimension=mx_provider GET /v1/analytics allowed allowed
  4. get_status GET /v1/status allowed allowed
  5. destroy_suppression sam@example.com DELETE /v1/suppressions/:id allowed allowed
  6. suspend_tenant acme POST /v1/tenants/:id/suspend 403 forbidden allowed
  7. create_cluster name=staging POST /v1/clusters 403 forbidden allowed
  8. create_smtp_credential production POST /v1/clusters/:cluster_id/smtp_credentials 403 forbidden allowed
  9. send_email to=alex@example.com POST /v1/emails 403 forbidden allowed

5 of 109 tools. Every other call returns 403 forbidden.

All 109 tools, behind the same KYC, payment, and send gates.

What Support can see Managing API keys

Answer delivery questions from your agent.

Any MCP client that sends a Bearer header works. Cursor is the documented path.

Start free trial Why PostShiba?