MCP Redis vs Zektor — MCP Server Comparison | AllMCPs
MCP Redis vs Zektor
A side-by-side look at the MCP Redis and Zektor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Redis for databases work as a local process; choose Zektor for databases. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Redis when
You need dedicated capabilities in the Databases domain.
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.
No confirmed install command for Zektor yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Redis is categorized under Databases and uses a local stdio subprocess. Zektor belongs to Databases and uses an install path we have not confirmed yet. Pick MCP Redis for databases work and Zektor for databases.
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. Zektor has no confirmed install command yet — follow its own setup instructions.
MCP Redis is listed as free. Auth: other. Zektor has no declared pricing — check the project's own site. Auth: api key required. 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 redis-mcp-redis and zektor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Redis has a quality signal of 81/100 (Excellent) with 6 views, 0 installs and 632 GitHub stars. Zektor has 32/100 (Emerging) with 0 views, 0 installs and 1 GitHub stars.