littlebird-mail
Allows sending and receiving emails through Cloudflare Email Routing and Workers, with tools for inbox management, replying, searching, and statistics.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@littlebird-mailsend an email to support@example.com with subject 'Question' and body 'Need help'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
littlebird-mail
Littlebird's independent mailbox - a Cloudflare Worker that acts as a remote MCP server for send, read, reply, and search.
What it does
Outbound: Sends email as
littlebird-mail@workslo.aivia Cloudflare'ssend_emailWorker binding. DKIM-signed, so it lands as Littlebird - not Shane.Inbound: Receives email via Cloudflare Email Routing, parses with
postal-mime, and stores in D1.MCP Tools: Six tools exposed over a stateless HTTP endpoint (
/mcp):send_email- Send mail as Littlebirdreply- Reply to an existing threadlist_inbox- Paginated inbox list, optional unread-only filterread_message- Full message body + marks as readsearch_inbox- Text search across subject, body, and frominbox_stats- Total and unread counts
Related MCP server: Remote MCP Server (Authless)
Architecture
Stateless: No Durable Objects or session state. All persistence is D1.
Auth:
/mcpis guarded by a Bearer token (MCP_TOKENsecret).Threading: Unified
messagestable withthread_idandin_reply_to. Replies attach to the parent thread.
Deploy
1. Domain setup (alive-node only)
Onboard
workslo.aito Cloudflare Email Service (Dashboard: Compute & AI > Email Service > Onboard Domain).Add SPF + DKIM records as instructed.
2. Install & deploy
npm install
npx wrangler deploy3. Set secrets
npx wrangler secret put MCP_TOKEN
# Enter a long random string (this guards /mcp)4. Inbound routing rule
Dashboard: Email Service > Email Routing > Create rule
Custom address:
littlebird-mail@workslo.aiAction: Send to a Worker
Worker:
littlebird-mail
5. Wire up the MCP client
In Littlebird Settings > Integrations, add a Remote MCP server:
URL:
https://littlebird-mail.<your-subdomain>.workers.dev/mcpAuth: Bearer token = the value you set in step 3
Schema
D1 database littlebird-mail was provisioned manually. If you start fresh, run:
CREATE TABLE IF NOT EXISTS messages (
id INTEGER PRIMARY KEY AUTOINCREMENT,
direction TEXT NOT NULL, -- 'inbound' or 'outbound'
from_address TEXT,
to_address TEXT,
subject TEXT,
body_text TEXT,
body_html TEXT,
thread_id TEXT,
in_reply_to TEXT,
message_id TEXT UNIQUE,
created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
read_at DATETIME,
labels TEXT,
raw_headers TEXT
);
CREATE INDEX IF NOT EXISTS idx_thread ON messages(thread_id);
CREATE INDEX IF NOT EXISTS idx_created ON messages(created_at);
CREATE INDEX IF NOT EXISTS idx_in_reply_to ON messages(in_reply_to);
CREATE TABLE IF NOT EXISTS config (
key TEXT PRIMARY KEY,
value TEXT
);D1 Database ID
Name:
littlebird-mailID:
dbc3a61d-e581-4b03-9296-eee97dfb5851Region: WNAM
Environment
Binding | Name | Purpose |
D1 |
| Message store + config |
send_email |
| Outbound mail |
var |
| Default From address |
secret |
| Bearer auth for /mcp |
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shaneslo/littlebird-mail'
If you have feedback or need assistance with the MCP directory API, please join our Discord server