Postfleet

ai.postfleetPublished by postfleet.aiOfficial publisherv0.1.4Updated Oct 24, 2026

Give an AI agent its own email address: send, reply, read, and wait for mail.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Gives an AI agent its own email address so it can send, reply to, read, and wait for mail through Postfleet.

What you can do
Postfleet provides email infrastructure for agents. The tools cover mailbox and domain management (list and create mailboxes, list, create and verify domains), sending and replying to email, and reading mail (list inbox, read email, wait for email). A draft lifecycle (create, list, get, update, send, delete) supports flows where a human approves before mail goes out; a gated send returns 202 pending_approval rather than failing. Each tool calls the same REST API endpoints the key already reaches, so auth, scoping and quotas are enforced once.
When to use it
Use it when an assistant needs to operate an email inbox of its own: sending and replying to messages, polling for incoming mail, or preparing drafts for human approval before sending. It suits agent workflows that need a dedicated address rather than a shared human mailbox.
Requirements
Either the hosted endpoint at api.postfleet.ai over streamable HTTP with an Authorization bearer header, or the local npm package @postfleet/mcp run via npx with Node.js. A Postfleet API key (pf_...) is required, supplied as POSTFLEET_API_KEY or as the bearer token; the mcp-scoped key is the one intended for clients. POSTFLEET_API_URL can override the API origin. Network access to Postfleet is needed.
Before you install
The API key is a credential: keep it out of commits and use a separate key per workload so one can be revoked without breaking others. The server can send and reply to email on the agent's behalf, and can create mailboxes and domains, so outgoing mail and account changes should be reviewed. Prefer the draft approval flow where a human should sign off before mail is sent.

Installation

In SourceWeft

  1. Open Postfleet in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.postfleet%2Fpostfleet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "postfleet": {
      "type": "http",
      "url": "https://api.postfleet.ai/api/mcp"
    }
  }
}

README

Postfleet MCP

[Listed on mcpservers.org]

Give an AI agent its own email address. Postfleet is email infrastructure for agents — inbound is parsed, classified, extracted to your schema, and screened for prompt injection before your agent reads a word.

This repo holds the server source and its plugin manifests. It is a mirror — the code is developed in the Postfleet application repo and published to npm as @postfleet/mcp; open issues here, send patches here, and they land upstream. The server ships two ways:

Hosted (no install)https://api.postfleet.ai/api/mcp, streamable HTTP, Authorization: Bearer pf_...
Local (stdio)@postfleet/mcp via npx

Get a pf_ API key at postfleet.ai.

Tools

list_mailboxes, create_mailbox, list_domains, create_domain, verify_domain, send_email, reply_email, list_inbox, read_email, wait_for_email — plus the draft lifecycle (create_draft, list_drafts, get_draft, update_draft, send_draft, delete_draft) for flows where a human approves before mail goes out. A send that lands in that gate returns 202 pending_approval, which is not a failure.

Every tool is thin-over-REST — it calls the same /api/v1/ endpoints your key already reaches (OpenAPI), so auth, scoping, and quotas are enforced once.

Install

Cursor marketplace plugin

The manifests in this repo (mcp.json, .cursor-plugin/plugin.json) declare headers.Authorization = Bearer ${POSTFLEET_API_KEY} for the hosted server and the same variable for local npx @postfleet/mcp. Installing the plugin should prompt for that key and attach it as a real Bearer header — a raw URL add without the header will 401 on initialize until a key is supplied or the hosted connect card finishes OAuth.

Cursor (manual)

json
{  "mcpServers": {    "postfleet": {      "url": "https://api.postfleet.ai/api/mcp",      "headers": { "Authorization": "Bearer pf_your_key_here" }    }  }}

Local stdio (npx -y @postfleet/mcp)

bash
npx -y @postfleet/mcp

Any MCP client that speaks stdio can run that command with POSTFLEET_API_KEY set:

json
{  "mcpServers": {    "postfleet": {      "command": "npx",      "args": ["-y", "@postfleet/mcp"],      "env": { "POSTFLEET_API_KEY": "pf_your_key_here" }    }  }}

Claude Code

bash
claude mcp add postfleet --env POSTFLEET_API_KEY=pf_your_key_here -- npx -y @postfleet/mcp

POSTFLEET_API_URL (default https://api.postfleet.ai) overrides the API origin for staging or self-hosted deployments.

Keys

Keys are scoped — bootstrap can only create mailboxes, api covers mail operations, mcp is the one to hand a client. Use a separate key per workload so you can revoke one without breaking the rest. Never commit a key; the manifests in this repo deliberately contain none.

Links

Build from source

bash
npm install && npm run build   # tsup → dist/

MIT licensed.

Source: README.md at commit b835e9e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.4LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts