Bring Redis
to CrewAI
Create your Vinkius account to connect Upstash to CrewAI and start using all 23 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
Compatible with every major AI agent and IDE
What is the Upstash MCP Server?
Connect your Upstash Redis database to any AI agent and interact with your serverless data store through natural conversation — no Redis CLI needed.
What you can do
- Health Checks — Ping your database to verify connectivity and inspect server health
- String Operations — Get, set and delete key-value pairs with optional TTL management
- Hash Management — Store and retrieve structured data as field-value pairs within hash keys
- List Operations — Push, pop and range elements from Redis lists for queue and stack patterns
- Set Operations — Add, remove and query set membership for unique collections
- Key Discovery — List keys by pattern, check existence, inspect data types and view TTL values
- Numeric Operations — Increment and decrement counters atomically
- Pub/Sub Messaging — Publish messages to channels for event-driven architectures
- Pipeline Execution — Execute multiple commands in a single HTTP request for batch operations
How it works
- Subscribe to this server
- Enter your Upstash REST URL and Token
- Start managing your Redis data from Claude, Cursor, or any MCP-compatible client
No more switching to another terminal to run Redis commands. Your AI acts as an in-memory data engineer.
Who is this for?
- Backend Developers — manage caching layers, feature flags, session storage and rate limit counters directly from chat
- DevOps Engineers — monitor database health, audit key patterns and manage TTL-based data lifecycle
- Full-Stack Teams — manipulate data structures (hashes, lists, sets) for application state without opening Redis CLI
Built-in capabilities (23)
If the key does not exist, it is initialized to 0 before the operation. Returns the new value after decrementing. Decrement a numeric value in Upstash Redis
Returns 1 if the key was deleted, 0 if it did not exist. WARNING: this operation is irreversible. Delete a key from Upstash Redis
This is a lightweight way to check key presence without retrieving the value. Check if a key exists in Upstash Redis
The key will be automatically deleted when the TTL reaches zero. Returns 1 if the timeout was set, 0 if the key does not exist. Set a TTL on a key in Upstash Redis
Returns null if the key does not exist. This is the primary read operation for string data. Get a value from Upstash Redis
Returns null if the key or field does not exist. Get a field value from a Redis hash
Returns an object with all fields and their values. Returns an empty object if the key does not exist. Get all fields and values from a Redis hash
If the key does not exist, a new hash is created. If the field already exists, its value is overwritten. Returns the number of fields added (1 for new, 0 for updated). Set a field in a Redis hash
If the key does not exist, it is initialized to 0 before the operation. Returns the new value after incrementing. Increment a numeric value in Upstash Redis
Get the data type of a key in Upstash Redis
Use "*" for all keys, "prefix:*" for keys with a prefix, or "*:suffix" for suffix matching. WARNING: KEYS can be slow on large databases — use sparingly. List keys in Upstash Redis
Returns 0 if the key does not exist. Get the length of a Redis list
If the key does not exist, a new list is created. Returns the length of the list after the push. Push values to the left of a Redis list
Use 0 as start and -1 as stop to get all elements. Positive indices count from the head (0 = first), negative indices count from the tail (-1 = last). Get a range of elements from a Redis list
Commands are sent as a JSON array of arrays, e.g. [["SET","k1","v1"],["GET","k1"],["INCR","counter"]]. Returns an array of results in the same order. Note: the pipeline is NOT atomic (other commands may interleave) — use /multi-exec for atomicity. WARNING: this is a powerful tool — review commands carefully before execution. Execute multiple commands atomically via Upstash pipeline
Returns the number of subscribers that received the message. This is a fire-and-forget operation — subscribers must be actively listening. Publish a message to a Redis channel
If the key does not exist, a new list is created. Returns the length of the list after the push. Push values to the right of a Redis list
Duplicate members are ignored. If the key does not exist, a new set is created. Returns the number of members that were added. Add members to a Redis set
Optionally set an expiry time in seconds using the ex parameter. Overwrites any existing value at the key. Returns "OK" on success. This is the primary write operation for string data. Set a value in Upstash Redis
This is a fast O(1) membership check. Check if a member is in a Redis set
Returns an array of all unique members. Returns an empty array if the key does not exist. Get all members of a Redis set
Non-existent members are ignored. Returns the number of members that were removed. Remove members from a Redis set
Returns -1 if the key has no expiry, -2 if the key does not exist. Get the TTL of a key in Upstash Redis
Why CrewAI?
When paired with CrewAI, Upstash becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Upstash tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Upstash in CrewAI
Why run Upstash with Vinkius?
The Upstash connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 23 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.




Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Upstash using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Upstash and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Upstash to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Upstash for CrewAI
Every request between CrewAI and Upstash is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Where do I find my Upstash REST URL and Token?
Log in to the Upstash Console, select your Redis database, and look for the REST API section. You'll find the HTTPS Endpoint (your REST URL, e.g. https://xxx-yyy-12345.upstash.io) and the Token value. Copy both and paste them here. There are two token types: Standard (full access) and Read-Only (read-only commands). Use Standard for full functionality.
What Redis commands are supported via the REST API?
The Upstash REST API supports most Redis commands including: Strings (GET, SET, DEL, EXISTS, EXPIRE, TTL, INCR, DECR), Hashes (HSET, HGET, HGETALL), Lists (LPUSH, RPUSH, LRANGE, LLEN), Sets (SADD, SMEMBERS, SISMEMBER, SREM), Keys (KEYS, TYPE, PING), and Pub/Sub (PUBLISH). The pipeline endpoint allows executing multiple commands in a single request. Blocking commands (BLPOP, BRPOP) and WATCH/UNWATCH are not supported.
Can I execute multiple commands atomically?
The pipeline tool sends multiple commands in a single HTTP request for efficiency, but it is NOT atomic — other commands may interleave between them. For atomic multi-command execution, Upstash supports the /multi-exec endpoint (same syntax as pipeline but guarantees atomicity). However, this MCP server currently exposes the standard pipeline tool for batch operations.
Is the Upstash REST API rate-limited?
Upstash does not enforce a fixed RPS limit. Instead, your plan defines a daily command limit. Each REST call counts as one command (or multiple commands if using pipeline). If you exceed your daily limit, commands will fail with a 400 error. Check your Upstash console for current usage. For high-throughput scenarios, consider using the pipeline endpoint to batch multiple commands into single HTTP requests.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Hanko (Passkey Auth)
15 toolsManage passkey authentication and user identity via Hanko — initialize registrations, handle logins, and manage WebAuthn credentials directly.

Dailymotion Alternative
9 toolsManage your Dailymotion account — audit videos, playlists, and followers via AI.

MightyCall
6 toolsSet up a professional virtual phone system with call routing, voicemail, and analytics that makes your small team sound big.

Moosend (Email Marketing & Automation)
10 toolsManage email marketing via Moosend — create campaigns, track mailing lists, and audit performance analytics.
