MCP emails
MCP emails for developers. Point Cursor, Claude, or your own agent at the same mailbox tools Companion uses — inbox, calendar, tasks, team.
Mail for developers
Humaner MCP emails give your agent the same mailbox Companion uses. Inbox, calendar, tasks, and team — over MCP. Mail for developers who already live in Cursor or Claude.
Connect
- 1
Frontier
MCP emails are included on Frontier. Companion already lives in the workspace — this is only if you want your own agent on the same mailbox.
Upgrade - 2
Pick your AI tool
We'll give you the exact command to run.
- 3
terminal
claude mcp add humaner --scope user --transport http https://app.humaner.io/api/mcp - 4
Enable Humaner
Start a Claude Code session, then run the command below. Select humaner.
terminal
claude /mcp - 5
Authorize
Select Authenticate. Sign in to Humaner in the browser and approve mailbox — calendar or intelligence if you want them.
Revoke a client anytime in Settings → MCP → Connected clients.
Knowledge search vs Hybrid RAG
When intelligence is handed to MCP, your agent gets `search_knowledge` — Postgres full-text search over the same workspace knowledge. That is not Hybrid RAG. Companion keeps semantic vectors, BM25 fusion, and rerank in-app.
| Companion | MCP | |
|---|---|---|
| Hybrid RAG | Yes — vectors + BM25 + rerank | No |
| Knowledge search | Via Hybrid RAG | Yes — FTS, included allotment |
| Memory & learning | Yes | No |
| Credits | Companion replies | Not for knowledge search |
Hand intelligence to MCP
Settings → MCP. Turning intelligence on for MCP hides Companion in-app and exposes `search_knowledge` to your own agent.
Verify
List tools. You should see mailbox, calendar, and task actions on your aliases. With intelligence on MCP, you also see `search_knowledge`.