Gotify RMCP vs Call4me
A side-by-side look at the Gotify RMCP and Call4me 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 Call4me for communication over a hosted endpoint. 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 Call4me when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 43/100 · Fair | 79/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 2 | 14 |
| Directory activity | 1 views 0 installs 0 upvotes | 16 views 2 installs 2 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gotify RMCP | View Call4me |
Tools & capabilities
Gotify RMCP tools
No tool names declared yet. Check the project README from the listing page.
Call4me 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"
]
}
}
}
Call4me
{
"mcpServers": {
"call4me": {
"url": "https://call4.me/mcp"
}
}
}
Frequently asked questions
Gotify RMCP is categorized under Communication and uses a local stdio subprocess. Call4me belongs to Communication and uses a remote HTTP/SSE transport. Pick Gotify RMCP for communication work and Call4me 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. Call4me is listed as a paid service. Auth: oauth 2.0. 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 call4me 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. Call4me has 79/100 (Great) with 16 views, 2 installs and 14 GitHub stars.