RuSender vs Unisender MCP
A side-by-side look at the RuSender and Unisender MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose RuSender for marketing work over a hosted endpoint; choose Unisender MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose RuSender when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Choose Unisender MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
UNISENDER_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 40/100 · Fair | 28/100 · Emerging |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | UNISENDER_API_KEY |
| Verified owner | Community listing |
Tools & capabilities
RuSender tools
No tool names declared yet. Check the project README from the listing page.
Unisender MCP 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.
RuSender
{
"mcpServers": {
"rusender": {
"url": "https://mcp.rusender.ru/mcp"
}
}
}
Unisender MCP
{
"mcpServers": {
"unisender-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/unisender-mcp"
],
"env": {
"UNISENDER_API_KEY": "YOUR_UNISENDER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
RuSender is categorized under Marketing and uses a remote HTTP/SSE transport. Unisender MCP belongs to Marketing and uses a local stdio subprocess. Pick RuSender for marketing work and Unisender MCP for marketing.
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.
RuSender has no declared pricing — check the project's own site. Unisender MCP 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 rusender and unisender-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, RuSender has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Unisender MCP has 28/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.