
Sealedmail
io.github.thesuitabsPublished by GitHub account thesuitabsv0.1.1Updated Oct 24, 2026
Send and receive on-chain private messages via SealedMail on Sui. No browser wallet needed.
Overview
Lets an assistant send and receive private on-chain messages through SealedMail on the Sui blockchain, without a browser wallet.
- What you can do
- This local MCP server connects an assistant to SealedMail, a private messaging service on the Sui blockchain. It exposes tools for sending and receiving on-chain private messages, so an assistant can compose and dispatch messages and read incoming ones on the user's behalf. It runs as a local process over stdio and does not require a browser wallet extension.
- When to use it
- Use it when you want an assistant to handle private on-chain messaging on Sui, for example sending or checking SealedMail messages during an agent workflow. It is not useful if you do not already use SealedMail or hold a Sui wallet.
- Requirements
- Runs locally as an npm package (npx sealedmail-mcp) over stdio, so Node.js is needed. It requires the environment variable SEALEDMAIL_PRIVATE_KEY, a Sui wallet private key in suiprivkey1... format exported with sui keytool export. Desktop only; no browser or web execution.
Installation
In SourceWeft
- Open Sealedmail 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
SealedMail MCP Server
Lets AI agents send and receive on-chain private messages via SealedMail on Sui — no browser wallet needed.
Install
See full docs at https://github.com/thesuitabs/sealedmail
Source: README.md at commit 7e4f1b3
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
40% 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
- License10 pts
Declare a license in the repository or the registry entry.