
Mcp Email
io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026
Email for AI agents — read inbox (IMAP), search, and send (SMTP).
Overview
Lets an assistant read, search, and send email through IMAP and SMTP from a local process.
- What you can do
- This server gives an assistant email capabilities: reading an inbox over IMAP, searching messages, and sending mail over SMTP. It runs locally as an npm package over stdio, so the assistant talks to it on the user's machine rather than to a hosted endpoint. The manifest lists no tools, so the exact tool names and parameters are not documented here.
- When to use it
- Worth adding when an assistant needs to work with an existing mailbox — triaging or searching messages, or composing and sending replies — without a separate email client. It suits desktop setups, since the manifest marks it desktop only and not web executable.
- Requirements
- Runs as a local process via the npm package @infoinlet/mcp-email over stdio, so Node.js and npm are needed. The manifest declares no authentication, environment variables, or headers, but IMAP and SMTP access normally requires a mail server address plus account credentials, which are not described in the available input.
Installation
In SourceWeft
- Open Mcp Email in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.