Send and receive email from CrewAI
Give CrewAI a real email address. ThreadCamp provides programmatic inboxes, Resend-compatible sending and forwarding Routes through one REST API and an MCP server - so CrewAI can send, receive OTPs and hold conversations.
Wire up the MCP server
CrewAI speaks the Model Context Protocol, so you can attach ThreadCamp's MCP server and the agent gains tools like create_inbox, send, wait_for_message and forward. Add the server to your CrewAI configuration:
{
"mcpServers": {
"threadcamp": {
"command": "npx",
"args": ["-y", "@threadcamp/mcp"],
"env": { "THREADCAMP_API_KEY": "sk_live_..." }
}
}
}
// Or point at the hosted server:
// { "url": "https://threadcamp.vercel.app/mcp",
// "headers": { "Authorization": "Bearer sk_live_..." } }Receive and forward, not just send
Sending is only half the loop. Create an inbox with POST /v1/inboxes to get a real, addressable mailbox with threads. Inbound mail arrives over HMAC-signed webhooks or polling, and per-domain Routes can forward mail - with SRS so SPF and DMARC survive - to another address, a webhook, or straight into a ThreadCamp inbox that CrewAI can reply on.
Other frameworks
Email from Vercel AI SDK
Inboxes, sending and forwarding via one key.
Email from LangChain
Inboxes, sending and forwarding via one key.
Email from OpenAI Agents SDK
Inboxes, sending and forwarding via one key.
See the wider email platform for AI agents and the one email API that powers it.
Questions
How do I add email to CrewAI?
Add the ThreadCamp MCP server to CrewAI and the agent gets tools to create an inbox, send, wait for a message and forward. You can also call the REST API at /v1/emails directly with a scoped API key.
Can CrewAI receive replies, not just send?
Yes. Create an inbox with POST /v1/inboxes and read inbound mail via HMAC-signed webhooks or polling. Threads and messages are first-class objects, so CrewAI can send, receive and forward under one key.
Give CrewAI an inbox in the next minute.
No credit card. Full API, MCP and webhooks on the free tier.