Connect Claude
Faivelo ships a hosted MCP (Model Context Protocol) server, so you can connect Claude directly to your mailboxes — read, search, send, and tidy up your mail by just asking. Setup takes about a minute, and there are no API keys to copy around: you sign in, pick exactly which mailboxes Claude may touch, and approve.
You need an active paid Faivelo plan to use the connection.
Connect claude.ai
- In claude.ai, open Settings → Connectors.
- Click Add custom connector and paste:
https://faivelo.com/api/mcp - Your browser opens the Faivelo sign-in page — log in if you aren't already.
- On the consent screen, choose which of your mailboxes Claude may access. Only the mailboxes you tick are reachable — everything else on your account stays invisible.
- Optionally tick Allow creating new mailboxes if you want Claude to be able to provision new addresses on your domains (capped at 10 per day; new mailboxes it creates are added to the connection automatically).
- Click Approve. That's it — no keys to copy, nothing to paste back.
Connect Claude Code
One command:
claude mcp add --transport http faivelo https://faivelo.com/api/mcp
The first time Claude Code uses the connector, it opens the same Faivelo sign-in and mailbox picker in your browser.
What Claude can do
Once connected, Claude gets a full mail toolset — scoped to the mailboxes you selected:
| Ability | Tools |
|---|---|
| Get oriented | list_mailboxes, list_domains, get_account_summary (send quota used/remaining), get_setup_summary (a shareable summary of what is set up) |
| Read mail | list_messages, read_message, get_thread (whole conversations), search_messages, search_all_mailboxes (one query across every shared mailbox), list_folders, get_attachment |
| Look up contacts | get_contacts |
| Send mail | send_message — supports attachments and a sendAt time; counts against your plan's send allowance |
| Drafts and scheduled sends | create_draft, update_draft, send_draft (leave a reply in Drafts for you to check first), list_scheduled, cancel_scheduled |
| Manage messages | flag_message, label_message, mark_all_read, move_message, restore_message, mark_spam, delete_message, empty_trash |
| Manage aliases | list_aliases, create_alias, delete_alias — aliases may only route to the mailboxes you shared |
| Check deliverability | get_delivery_status — did mail to a recipient bounce, are they suppressed? |
| Browse Drive | drive_list_files, drive_download_file — only appear if you granted Drive access during consent |
| Create mailboxes | create_mailbox — only appears if you opted in during consent |
| Manage DNS | list_dns_records, create_dns_record, update_dns_record, delete_dns_record — API keys with the dns:read / dns:write scopes only, not Claude connections |
Connections made before the toolset expanded won't have alias permissions. Disconnect and reconnect the Faivelo connector to pick up the full set.
Things to try
- "Summarize my unread mail."
- "Find the invoice from Acme and reply that payment is on the way."
- "Search support@ for anything mentioning refunds this week and give me a rundown."
- "Move all the newsletters in my inbox to the Newsletters folder."
Managing and revoking access
Every connection is listed in your Faivelo dashboard under Settings → Connected Apps. You can see what each app can reach and revoke it with one click — revoking cuts access instantly.
Security
- You choose the blast radius. Claude can only reach the mailboxes you picked on the consent screen — never your other mailboxes, domains, billing, or account settings.
- Tokens expire and rotate. Access tokens are short-lived (one hour) and refreshed automatically with rotating refresh tokens. If a rotated token is ever replayed, the whole connection is revoked as a precaution.
- Everything is revocable. Remove the connection from Settings → Connected Apps at any time, and access stops immediately.
Sending through the connector uses your plan's normal monthly send allowance, and message actions (delete, move, mark spam) are real — Claude asks before doing anything destructive, but the changes it makes are the same as if you'd made them in webmail.
Next steps
- Building a headless agent instead? See AI agents & API keys for scoped API keys and the same MCP server with Bearer auth.