Where do I find my Upstash REST URL and Token?

Log in to the [**Upstash Console**](https://console.upstash.com), 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.

Upstash MCP Server for CrewAI 23 tools — connect in under 2 minutes

Name: Upstash
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 23 Tools Framework

Connect your CrewAI agents to Upstash through Vinkius, pass the Edge URL in the `mcps` parameter and every Upstash tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Upstash Specialist",
    goal="Help users interact with Upstash effectively",
    backstory=(
        "You are an expert at leveraging Upstash tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Upstash "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 23 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About 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.

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.

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

The Upstash MCP Server exposes 23 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Upstash to CrewAI via MCP

Follow these steps to integrate the Upstash MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 23 tools from Upstash

Why Use CrewAI with the Upstash MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Upstash through the Model Context Protocol.

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 `mcps` parameter 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 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Upstash MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Upstash for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Upstash, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Upstash tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Upstash against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Upstash MCP Tools for CrewAI (23)

These 23 tools become available when you connect Upstash to CrewAI via MCP:

decr

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

del

Returns 1 if the key was deleted, 0 if it did not exist. WARNING: this operation is irreversible. Delete a key from Upstash Redis

exists

This is a lightweight way to check key presence without retrieving the value. Check if a key exists in Upstash Redis

expire

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

get

Returns null if the key does not exist. This is the primary read operation for string data. Get a value from Upstash Redis

hget

Returns null if the key or field does not exist. Get a field value from a Redis hash

hgetall

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

hset

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

incr

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

key_type

Get the data type of a key in Upstash Redis

list_keys

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

llen

Returns 0 if the key does not exist. Get the length of a Redis list

lpush

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

lrange

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

pipeline

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

publish

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

rpush

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

sadd

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

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

sismember

This is a fast O(1) membership check. Check if a member is in a Redis set

smembers

Returns an array of all unique members. Returns an empty array if the key does not exist. Get all members of a Redis set

srem

Non-existent members are ignored. Returns the number of members that were removed. Remove members from a Redis set

ttl

Returns -1 if the key has no expiry, -2 if the key does not exist. Get the TTL of a key in Upstash Redis

Example Prompts for Upstash in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Upstash immediately.

"Check if my Upstash Redis database is responding."

"Set a feature flag called 'dark_mode' to true for user 'user123' with a 1 hour expiry."

"Show me all keys matching the pattern 'session:*' and check their data types."

Troubleshooting Upstash MCP Server with CrewAI

Common issues when connecting Upstash to CrewAI through the Vinkius, and how to resolve them.

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.

Upstash + CrewAI FAQ

Common questions about integrating Upstash MCP Server with CrewAI.

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.