Upstash MCP connector
The Upstash connector brings your Redis databases, backups, QStash schedules, message queues and vector indexes to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person works with them under their own access and every action is logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
55 tools
How to connect
How to connect Upstash to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Upstash once
-
Open Connections, choose Add connection, and pick Upstash.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Upstash. Upstash's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Upstash MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Upstash MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Upstash MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Upstash to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Upstash through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Platform
Check a Redis database before a launch
Ask for memory use, request counts and eviction settings on the database behind tomorrow's release, and get a plain answer without opening the console.
-
Engineering
Take a backup before a risky change
Have the agent create a backup of the sessions database, confirm it finished, and list the recent backups so you know there is something to roll back to.
-
Operations
Clear the dead letter queue after an outage
See which messages landed in the dead letter queue overnight, decide what to retry or drop, and clear it once the downstream service is back.
-
Engineering
Pause a QStash schedule for the weekend
Pause the nightly export schedule before a maintenance window, then resume it on Monday, without hunting for the schedule in the dashboard.
-
Data
See what a vector index holds
Ask how many vectors are in the product search index, what dimension it uses, and when it was last updated before you point a new feature at it.
-
Support
Trace a failed message through the logs
When a customer reports a missing webhook, pull the QStash logs for that message and find out whether it was delivered, retried or dropped.
Try asking
- “Which Redis databases have no backup from this week?”
- “Show me what is sitting in the dead letter queue.”
- “Pause the nightly report schedule in QStash until Monday.”
Compare
Elaichi vs Zapier MCP vs Composio for Upstash
All three can connect Upstash to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Upstash tools | Allow or restrict single Upstash tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Upstash call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Upstash tools for your AI agents
55 tools are ready to call through Elaichi's MCP endpoint the moment you connect Upstash, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Upstash builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Upstash gets you
6 screens from the product, each doing one job for your Upstash account.
The agent
Ask about your Redis databases in plain language.
Answers come from live Upstash databases, backups and QStash schedules, not from a stale export.
- databases
- backups
- schedules
- indexes
Ask Elaichi to work across your apps.
Which Redis databases have no backup from this week?
Show me what is sitting in the dead letter queue.
Pause the nightly report schedule in QStash until Monday.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Upstash to every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
55 Upstash tools, ready without writing code.
Databases, backups, QStash schedules, dead letter queues and vector indexes, covered with no custom code.
- Redis list databases
- Redis get database
- Redis get stats
- Redis list backups
ElaichiToolsToolboxes
Each team gets its own Upstash toolbox.
Platform keeps database management, operations keeps queues, and nobody sees more than their job needs.
- Platform
- Engineering
- Operations
- Data
ElaichiToolboxesShared connections
Share one Upstash connection, never a credential.
Teammates work through the shared account while the credential stays with the person who connected it.
- Platform
- Production
- Staging
- Operations
ElaichiConnectionsAudit log
Every Upstash action is logged with a name.
See who deleted a database, cleared a queue or changed a schedule, and when.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and the digest gets written.
Upstash databases are fetched, grouped and summarized, a person approves, then it posts back.
Upstash digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch databases
Upstash
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Upstash
Queued
Collections and dashboards
Upstash health numbers arrive without anyone asking.
Four metrics, 14 days of databases created and a team breakdown, refreshed with no model involved.
Upstash health
Refreshed 4 minutes ago · every 15 minutes · from the databases collection
Databases
1,284 ↓ 12%
Backups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Databases created
Last 14 days
By team
Share of activity
Platform 34%
Production 27%
Staging 21%
Operations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Upstash to Claude?
Connect Upstash in Elaichi first, signing in to your Upstash account over OAuth with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi and your Upstash connection is ready to use.
Does Upstash work with ChatGPT and Cursor as well as Claude?
Yes. Once Upstash is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Upstash once and every client picks it up.
What can an AI agent actually do with my Upstash data?
An agent connected to Upstash can list your Redis databases, report their memory and request stats, take or list backups, create or rename a database, and run a command against one. It can also publish messages and manage schedules in QStash, read logs, clear a dead letter queue, and tell you what a vector index holds. Short concrete asks work best, such as 'back up the sessions database' rather than a long paragraph.
Does connecting Upstash give the AI access to every database in my account?
No more than you already have. The AI works inside the Upstash access of the person who signed in, so it sees only the databases, schedules and indexes that person can see. Elaichi can narrow that further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Upstash?
Yes. Restrictions in Elaichi apply per action, so you can allow reading database stats and listing backups while blocking deleting a database, changing eviction settings or clearing a queue. A restricted Upstash action is never advertised to the AI client at all, so no prompt can reach it.
What happens to an Upstash connection when someone leaves?
Offboarding that person in Elaichi ends their access to Upstash through every client at once. A shared Upstash connection keeps working for everyone else on the team. If you want the connection gone entirely, disconnect Upstash once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client.
Does the Upstash MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Upstash is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Upstash?
Yes. Both let Claude, ChatGPT or Cursor use Upstash. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Upstash call.
How is Elaichi different from Composio for Upstash?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Upstash: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Upstash in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.