Redis MCP Server vs Slack MCP Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Redis MCP Server MCP Servers	Slack MCP Server MCP Servers
Tagline	Archived reference MCP server exposing basic Redis set/get/delete/list to any MCP-capable LLM client.	Archived reference MCP server that lets Claude and other MCP clients read and post in a Slack workspace via a bot token.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT). Self-hosted; you supply your own Redis instance.	Free· Free / open-source (MIT). Requires a Slack workspace and a Slack bot token; Slack itself is free/paid.
Model	—	—
Editorial score	—	—
Use cases	Agent short-term memorySession state for chat agentsFeature-flag lookup from an LLM tool callRate-limit counters queried by an agentPrototype MCP integrationsSimple cache for RAG intermediate resultsQueue-style scratchpad between agent steps	Channel triage and summarisationAutomated thread digestsPosting AI-generated status updatesCross-channel search and reportingStandup and retro note postingOn-call escalation repliesUser and profile lookup for routingReaction-based workflow signallingMCP server reference implementation
Pros	Zero-config for the common case: one Redis URL and you are done Ships as both NPX and Docker, plus one-click VS Code / VS Code Insiders install MIT licensed and small enough to fork and audit end-to-end Exponential-backoff retry (up to 5 attempts) smooths over transient network blips Reference implementation from the MCP maintainers, so the tool schemas are canonical	Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke Open-source under MIT, so forking or vendoring for internal hardening is straightforward Good starting point for learning how to write your own MCP server against a REST API
Cons	Archived on 29 May 2025 and no longer receiving updates or security fixes Only covers basic KV operations: no hashes, sets, sorted sets, streams, pub/sub, or RedisJSON/RediSearch list uses KEYS-style patterns, which can block on large production databases No built-in auth beyond whatever the Redis URL carries; you must protect the endpoint yourself For active development, Redis's own Python-based mcp-redis server is now the recommended path	Archived by the maintainer on 29 May 2025 — no upstream bug fixes, security patches, or Slack API compatibility updates Read-only surface for channels (public channels only by default) and no DM, private-channel, search, files, or canvas support out of the box No pagination helpers or rate-limit backoff beyond what the Slack SDK provides, so bulk history pulls in large workspaces can be fragile Requires a workspace admin to install a bot app and mint a token, which is a real blocker in locked-down enterprise Slack tenants Bot-token model means every action is attributed to the bot user, not the human operating the assistant, which complicates audit trails
Website	github.com	github.com

Pick Redis MCP Server if

✅ Zero-config for the common case: one Redis URL and you are done
✅ Ships as both NPX and Docker, plus one-click VS Code / VS Code Insiders install
✅ MIT licensed and small enough to fork and audit end-to-end
✅ Exponential-backoff retry (up to 5 attempts) smooths over transient network blips

Pick Slack MCP Server if

✅ Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well
✅ Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony
✅ Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet
✅ Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke

Compare a different pair →