Gotify RMCP vs Mailtea
A side-by-side look at the Gotify RMCP and Mailtea MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gotify RMCP for communication work as a local process; choose Mailtea for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gotify RMCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
Choose Mailtea when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 43/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gotify RMCP | View Mailtea |
Tools & capabilities
Gotify RMCP tools
No tool names declared yet. Check the project README from the listing page.
Mailtea tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gotify RMCP
{
"mcpServers": {
"gotify-rmcp": {
"command": "npx",
"args": [
"-y",
"@dinglebear/rgotify"
]
}
}
}
Mailtea
{
"mcpServers": {
"mailtea": {
"command": "npx",
"args": [
"-y",
"plugins"
]
}
}
}
Frequently asked questions
Gotify RMCP is categorized under Communication and uses a local stdio subprocess. Mailtea belongs to Communication and uses a local stdio subprocess. Pick Gotify RMCP for communication work and Mailtea for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Gotify RMCP has no declared pricing — check the project's own site. Mailtea has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gotify-rmcp and mailtea as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gotify RMCP has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 2 GitHub stars. Mailtea has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.