Linear MCP Server vs Redis MCP Server

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

	Linear MCP Server MCP Servers	Redis MCP Server MCP Servers
Tagline	Open-source MCP server bridging LLM agents to Linear's issue tracker (now deprecated in favour of Linear's official remote MCP)	Archived reference MCP server exposing basic Redis set/get/delete/list to any MCP-capable LLM client.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT). Requires a Linear account and personal API key; Linear itself is free for small teams, $8/user/mo Standard, $14/user/mo Plus.	Free· Free and open source (MIT). Self-hosted; you supply your own Redis instance.
Model	—	—
Editorial score	—	—
Use cases	Filing bugs from Claude Desktop or Cursor without leaving the editorAgent-driven triage of the inbox projectBulk relabeling or reprioritising issues via natural languageStandup summaries of a user's assigned Linear workAdding comments to tickets from a coding agent's PR reviewReference implementation for building a custom Linear MCP server	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
Pros	Open source (MIT) and small enough to read end-to-end in an afternoon One-line install via Smithery or straight npx in Claude Desktop config Covers the create / update / search / comment loop that 90% of ticket workflows need Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents) Clear tool schemas make it a good reference implementation for building your own MCP servers Uses Linear's official GraphQL API, so permissions and audit trails stay intact	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
Cons	Officially deprecated by its author in favour of Linear's own remote MCP server at mcp.linear.app/sse Runs as a local stdio process, so it has to be installed on every workstation and cannot be shared across a team Uses a personal API key, meaning every action shows up as the key owner rather than the actual LLM user Tool coverage is narrower than the official server: no cycles, projects, roadmaps, or workflow state management Error handling and rate-limit backoff are minimal; heavy agent loops can trip Linear's API limits	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
Website	github.com	github.com

Pick Linear MCP Server if

✅ Open source (MIT) and small enough to read end-to-end in an afternoon
✅ One-line install via Smithery or straight npx in Claude Desktop config
✅ Covers the create / update / search / comment loop that 90% of ticket workflows need
✅ Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents)

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

Compare a different pair →