Create a key to copy examples filled with your team.

Create an account Sign in

Connect MCP

Talk to the catalog API from Cursor with the same Developers token.

Cursor talks to PostShiba at /mcp on the dashboard host with Streamable HTTP. Use the platform application access token from Developers. That token is a team admin token. Claude Connectors and ChatGPT OAuth are not this path.

Issue a token

  1. Open the dashboard.
  2. Go to Developers → Platform applications.
  3. Create an application if you do not have one.
  4. Copy the access token from the tokens table. Do not copy the application uid or secret.

Add the server

Paste this into your MCP config. Replace YOUR_API_KEY with the access token.

mcp.json
1 {
2 "mcpServers": {
3 "postshiba": {
4 "url": "https://app.postshiba.com/mcp",
5 "headers": {
6 "Authorization": "Bearer YOUR_API_KEY"
7 }
8 }
9 }
10 }

The URL is https://app.postshiba.com/mcp. Do not point Cursor at https://postshiba.com. Query-string tokens are rejected.

What the token can do

The tools are the catalog REST API. team_id is taken from the token. The same KYC, payment, and send gates apply.

What it cannot do

A pending team can create one shared-IP cluster and can create inboxes. Send to anyone except team member emails and live inbox addresses returns 403 {"error":"kyc_required"} until the team is approved. A second cluster while pending also returns kyc_required.

MCP cannot publish DNS. After create_sending_domain, publish the DKIM and return-path CNAMEs at your registrar, then call verify_sending_domain.

MCP redacts inbox and webhook secrets. Copy those from the dashboard.

Cluster create issues a default SMTP user and hides the password. Call create_smtp_credential if you need a password in the tool result.

send_email picks the first sending-ready cluster and has no sandbox. send_on_cluster takes a cluster id and accepts sandbox: true. MCP cannot set Idempotency-Key. Both default From when it is blank or a platform-agent placeholder. They will not send as the whoami placeholder.

A hosted inbox is inbound only. MAIL FROM must be an address on a verified sending domain.

Questions you can ask

Paste one of these into Cursor after the server is connected.

create-cluster.txt
1 Create a shared-IP cluster for this team. Name it after the team. A pending team can create one. If create_cluster returns 403 kyc_required, the team already has a cluster and needs approval for another. KYC is not an MCP action. If it returns payment_required, stop. Poll get_cluster until sending_ready is true before you send. Until the team is approved, send only to team member emails and live inbox addresses. Anything else is 403 kyc_required.
create-credentials.txt
1 Create an SMTP credential on the cluster with create_smtp_credential so the password appears once. Cluster create already issues a default user and hides the password. Do not try to send over SMTP through MCP.
send-test-email.txt
1 Send a sandbox message with send_on_cluster and sandbox true. Do not use send_email for a sandbox send. A live send needs sending_ready, a verified From domain, and a live credential. MCP cannot set Idempotency-Key. Never use the whoami email as From. Omit from or use a verified sending domain.
create-mailbox.txt
1 Create a hosted inbox with create_inbox. Omit sending_domain_id so it stays hosted. Inbox create is open while KYC is pending. MCP redacts webhook_secret. Copy signing secrets from the dashboard inbox page, not from MCP.
send-from-domain.txt
1 Send from an address on a verified sending domain, not from the hosted inbox. Call create_sending_domain, wait while I publish the DKIM and return-path CNAMEs, then call verify_sending_domain. MAIL FROM cannot be an inbound.postshiba.com address. Never use the whoami email as From. Omit from or use a verified sending domain.

Previous

Create an API key

Next

Add and verify a domain

About

PostShiba is the transactional email platform that powers Bento behind the scenes. You can build your own products, like Bento, on top of it.

Product

© 2026 PostShiba by Backpack Internet Pty. Ltd. All rights reserved.

The same policies that govern Bento are applied to PostShiba → Privacy | Terms | Security