ToolsMCP
Mailoo - Email MCP Server
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- bitfloo (GitHub)
- Prerequisites
- Install @bitfloo/mailoo from npm (stdio transport). Declares 5 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.3.5 · updated
- Official links
Publisher’s description
Email MCP server for AI agents: IMAP/SMTP, Gmail, Outlook, calendar, ManageSieve, AI triage, OAuth2.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.3.5, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- bitfloo (GitHub)
- Version observed
- 0.3.5
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.Bitfloo%2Fmailoo/versions/0.3.5
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Read, draft and send email | Publisher description mentions “email”, “imap”, “gmail”, “triage”. | No connection check or task run. Capability is as described by the publisher. | Rule email matched: “email”, “imap”, “gmail”, “triage”. Rule email. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@bitfloo/mailoo(npm, stdio, 5 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.Bitfloo/mailoo
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.