Nextmail
sh.nextmailPublished by nextmail.shOfficial publisherv1.0.6Updated Nov 1, 2026
AI-native email for businesses, developers, and AI agents.
Overview
Remote Nextmail MCP server that lets an assistant send email and work through your own Nextmail mailbox under OAuth-approved permissions.
- What you can do
- Send email from an agent using the Nextmail SDKs, API or CLI
- Work through an inbox over MCP: read messages and make changes, with each tool marked as reading or changing
- Catch verification emails in sign-up tests using disposable inboxes
- Create a Nextmail account and verify it with a six-digit emailed code
- Follow guidance for moving an existing setup from Resend
- When to use it
- Useful when you want an assistant to send mail or triage an inbox from your own Nextmail workspace, or when tests need to receive verification emails. Also handy if you are migrating email sending from Resend.
- Requirements
- A remote endpoint at api.nextmail.sh/mcp reached over HTTPS; nothing runs locally. A Nextmail account, with OAuth sign-in in the browser where you choose permissions and allowed addresses. An account can be created by the agent, verified with a six-digit code sent to your email, which also yields an API key for the CLI and API.
Installation
In SourceWeft
- Open Nextmail in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/sh.nextmail%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"nextmail": {
"type": "http",
"url": "https://api.nextmail.sh/mcp"
}
}
}README
Nextmail for AI agents
Email for AI agents and for the people who build them, from Nextmail. This repository connects your agent to your own Nextmail mailbox, and teaches it the jobs people most often hand to an agent: sending email from code, working through an inbox, catching verification emails in tests, and moving from Resend.
What is in it
- One MCP server,
https://api.nextmail.sh/mcp, the remote server Nextmail runs. Your client signs in with OAuth in the browser, and on the consent page you choose which permissions and which addresses the agent may use. You can narrow or remove the connection later under Account, Connected apps. - Four skills, in
skills/: sending email with the SDKs, the API or the CLI; working in a mailbox over MCP; disposable inboxes for sign-up tests; and moving from Resend.
Install
Claude Code
Claude, ChatGPT and other chat apps. Add https://api.nextmail.sh/mcp as a custom connector.
Codex. Add this to ~/.codex/config.toml:
Gemini CLI
Any agent that reads skills
Cursor, VS Code, Windsurf and other MCP clients. See https://nextmail.sh/docs/mcp/connect.md
Any other agent. Ask it to read this one Markdown page, which says how to connect over MCP, the command line or the API, and what to ask you before it sends anything: https://nextmail.sh/agent.md
No account yet
An agent can create the account for you, and your only part is the six-digit code emailed to you. It starts a sign-up with your address at POST https://api.nextmail.sh/signups, you give it the code, and POST https://api.nextmail.sh/signups/{id}/verify creates the account and gives the agent an API key for the command line and the API. Neither call needs a key, and npx @nextmail/cli signup --email <address> does both steps. To connect over MCP as well, set a password from the welcome email, then sign in as above.
What it runs, sends and fetches
Nothing in this repository runs on your machine. The skills are written instructions, and the plugin adds one remote MCP server, which your client reaches over HTTPS at https://api.nextmail.sh/mcp once you have signed in. Its tools act on your Nextmail workspace, with the permissions you approved, and every tool is marked as reading or as making changes, so your client can ask before anything is sent or changed. The skills link to the documentation at https://nextmail.sh, and to the Nextmail SDK and CLI packages, which are installed only if you choose to.
Privacy, terms and support
- Privacy policy: https://nextmail.sh/privacy
- Terms: https://nextmail.sh/terms
- Support: [email protected]
- Documentation: https://nextmail.sh/docs/mcp/overview.md
License
MIT. See LICENSE.
Source: README.md at commit 3a319e8
Tools
0Version history
3- v1.0.6LatestNov 1, 2026
- v1.0.5Oct 25, 2026
- v1.0.3Oct 25, 2026
Score
85% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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
- License10 pts