Upstash Redis MCP Server

Official Upstash MCP server enabling AI agents to interact with Upstash's serverless Redis and Kafka — Redis data operations, database management, and Kafka topic interactions with per-request pricing.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Other upstash redis serverless mcp-server official edge rate-limiting queue
⚙ Agent Friendliness
84
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
85
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
82
Documentation
85
Error Messages
80
Auth Simplicity
88
Rate Limits
85

🔒 Security

TLS Enforcement
100
Auth Strength
78
Scope Granularity
65
Dep. Hygiene
85
Secret Handling
82

HTTPS enforced. Per-database REST tokens better than single API keys. SOC 2 Type II. Good serverless security posture.

⚡ Reliability

Uptime/SLA
88
Version Stability
85
Breaking Changes
85
Error Recovery
82
AF Security Reliability

Best When

An agent needs serverless, HTTP-based Redis access with pay-per-use pricing — ideal for edge deployments, low-traffic agents, or ephemeral storage.

Avoid When

You need persistent connections, Redis Cluster, or high-throughput low-latency caching at scale — use Redis Cloud directly.

Use Cases

  • Storing and retrieving agent context/memory in serverless Redis
  • Rate limiting implementation via Upstash Redis in agent workflows
  • Managing Upstash databases and configurations from agents
  • Queue and pub/sub operations via Upstash Kafka from agents
  • Edge-cached data access for globally distributed agent workflows

Not For

  • High-throughput persistent Redis workloads (Upstash has per-command pricing)
  • Teams requiring on-premises or VPC-only Redis
  • Workloads needing Redis Cluster or advanced data structure commands

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
No

Authentication

Methods: api_key rest_token
OAuth: No Scopes: No

REST API uses per-database REST tokens for data operations. Management API uses account-level API key. REST tokens provide database-level isolation.

Pricing

Model: usage-based
Free tier: Yes
Requires CC: No

Per-command pricing makes costs predictable for low-traffic agents. Free tier sufficient for development and low-volume production.

Agent Metadata

Pagination
cursor
Idempotent
Full
Retry Guidance
Documented

Known Gotchas

  • Per-command pricing means chatty agents accumulate costs quickly — batch operations where possible
  • REST API adds latency vs native Redis protocol — not suitable for sub-millisecond requirements
  • Daily command limits on free tier hit fast in agent testing loops
  • Management API vs data REST API use different auth tokens — configure both
  • Upstash Kafka is a separate product from Redis — different configuration required

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Upstash Redis MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5182
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered