Flowmails MCP
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Flowmails MCP
The hosted Model Context Protocol server for Flowmails — a custom-domain email platform built for AI agents.
Point any MCP client at https://sdk.flowmails.net/mcp with a Flowmails bearer token,
and the agent gets a mailbox on your own domain: send mail, read the inbox, search history,
and wait for an inbound message instead of polling.
Transport: MCP Streamable HTTP, JSON-RPC 2.0, protocol revision
2025-06-18Auth:
Authorization: Bearer <flowmails-api-key>(an SDK keyfm_…or an agent credentialagc_…)Tools: 12 (ten of them can change mailbox state; every call is scope-checked first)
Run it: hosted — nothing to install, no server to operate
Pricing: the platform's — Base is free, Pro $9.9/mo, Enterprise $39.9/mo. Your email provider bills you directly; Flowmails charges no per-email markup.
Why it exists
Most "email MCP servers" wrap an inbox API. This one is built around the hard part of agent workflows: waiting.
wait_for_email opens a durable wait on an address and a subject. The platform owns that
state, so the wait survives the edge, and the agent is handed the message when it lands — it
does not spin on an inbox polling loop. That is the difference between an agent that can run a
sign-up flow unattended and one that has to be babysat.
Sending is the same contract as the REST API and the official SDK: one key, bound to one domain, with an idempotency key and an audit trail behind every send.
Related MCP server: FrankKi MCP
Install
Claude Code / Claude Desktop
claude mcp add --transport http flowmails https://sdk.flowmails.net/mcp \
--header "Authorization: Bearer fm_..."Cursor / VS Code / Codex / any MCP client
{
"mcpServers": {
"flowmails": {
"url": "https://sdk.flowmails.net/mcp",
"headers": {
"Authorization": "Bearer fm_..."
}
}
}
}Any client, raw JSON-RPC
curl -X POST https://sdk.flowmails.net/mcp \
-H "Authorization: Bearer fm_..." \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'The tools
Tool | Scope | What it does |
|
| List the domains the credential can touch |
|
| List the inbound addresses of a domain |
|
| Provision a new inbound address |
|
| Search message history |
|
| Read one message (body, attachments, headers) |
|
| Send mail from a domain-bound address |
|
| Delivery status of a sent message |
|
| Open a durable wait on an address + subject |
|
| Check a wait (pending / resolved / expired) |
|
| Read the event log (cursor-based) |
|
| Claim a message so a second agent won't take it |
|
| Mark a claimed message as handled |
The scope check runs before the tool does, so a read-only credential cannot send, and a credential bound to one domain cannot touch another.
A typical agent flow
list_domains → create_address → wait_for_email → get_email → send_email → get_send_statusNo dashboard visit in between. The MCP server is the protocol-level door onto the same contract the REST API, the SDK and the CLI use.
Links
Landing page: https://flowmails.net/mcp
Documentation: https://flowmails.net/docs
For AI coding agents: https://flowmails.net/for/ai-coding-agents
OpenAPI 3.1: https://flowmails.net/openapi.json
SDK:
@flowmails/flowmails-sdk· CLI:@flowmails/cli
Registry metadata
This repository is the source of truth for the server's entry in the official MCP Registry:
see server.json. The name is io.github.wms-why/flowmails-mcp.
License
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted email for AI agents: create inboxes, send, receive, and reply over MCP with scoped API keys
Hosted email MCP for AI agents with inboxes, send/receive, memory, recovery, and credits.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI agents with a persistent, agent-native email mailbox for sending, receiving, and managing emails through bounded-context retrieval, idempotent operations, and explicit acknowledgement.MIT
- AlicenseNot gradedqualityBmaintenanceHosted remote MCP server that lets AI agents compose, price, send, and track real physical letters worldwide.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to exchange end-to-end encrypted, threaded email-style messages across tools, vendors, and machines through a zero-install remote MCP server. Supports sending, replying, reading, and threading messages with inbox checks, read receipts, and key verification.MIT

Escouade Mailofficial
AlicenseNot gradedqualityCmaintenanceProvides a hosted remote MCP server that lets AI agents create and use their own email address to send, receive, verify, and reply to messages.MIT