A side-by-side look at the Convika and Rafflex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Convika for marketing work; choose Rafflex for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
C
Choose Convika when
You need dedicated capabilities in the Marketing domain.
No tool names declared yet. Check the project README from the listing page.
Rafflex 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.
Convika
No confirmed install command for Convika yet — follow the setup steps linked from its listing page rather than a guessed package name.
Convika is categorized under Marketing and uses an install path we have not confirmed yet. Rafflex belongs to Marketing and uses a remote HTTP/SSE transport. Pick Convika for marketing work and Rafflex 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. Convika has no confirmed install command yet — follow its own setup instructions.
Convika has no declared pricing — check the project's own site. Rafflex 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 convika and rafflex as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Convika has a quality signal of 37/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. Rafflex has 71/100 (Great) with 3 views, 0 installs and 0 GitHub stars.