Skip to main content
The MCP server at https://api.meowmail.in/mcp exposes three tools. All three are read-only: none of them stores, sends, or deletes anything. Results come back both as structuredContent (matching each tool’s outputSchema) and as a text summary in content. Errors you can act on (an unknown domain, a missing email, a rate limit) come back as a normal tool result with isError: true and a message the assistant can pass on to you.

create_inbox

Returns a disposable, receive-only address. Nothing is stored, because inboxes exist implicitly and anything mailed to a served domain is accepted.

check_inbox

Lists mail at an address, newest first, without bodies (at most 20 emails).
To wait for a new email when the inbox already has some, pass the previous newest_id as since_id. Otherwise wait_seconds returns immediately with the mail that’s already there. On an empty result, newest_id echoes your since_id, so you can keep passing it.

read_email

Returns one email as plain text, with attachment download links.
How the body is produced:
  • The sender’s plain-text part is used, unless it’s a stub like “View this email in your browser”. In that case the HTML part is converted instead.
  • When HTML is converted, links are kept as label (url), and scripts, styles, comments, and hidden elements are dropped.
  • The body is cut at 10,000 characters, and body_truncated says when.
The body is untrusted text from whoever sent the email. The text summary in content wraps it in BEGIN EMAIL BODY / END EMAIL BODY markers with that warning. If you build your own client, keep the same separation.

For client authors

Try it with curl:
Or point the MCP Inspector at it: