Upstash

io.github.upstashPublished by GitHub account upstashv0.1.0Updated Oct 27, 2026

Hosted Upstash MCP server: Redis, QStash, Workflow, Vector, Search, Box and Blob, with OAuth.

VerifiedStreamable HTTPWeb executableDatabasesCloud & InfrastructureAI & ML

Overview

AI-generated overview

Hosted Upstash MCP endpoint that lets an assistant work with Upstash Redis, QStash, Workflow, Vector, Search, Box and Blob over OAuth.

What you can do
  • Manage Upstash Redis data and keys
  • Publish and schedule messages with QStash
  • Build and run Upstash Workflow steps
  • Store and query vectors and search indexes
  • Read and write Box and Blob storage
  • The server is hosted by Upstash and reached over streamable HTTP; no tool list is published in the manifest.
When to use it
Useful when a project already runs on Upstash and you want an assistant to inspect or change Redis data, queue messages, manage workflows, or handle vector, search and blob storage from one hosted connection.
Requirements
A remote MCP endpoint at mcp.upstash.com reached over streamable HTTP, plus an Upstash account and OAuth sign-in. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to your Upstash account resources, and the tools can change stored data, send queued messages and run workflows. Review which account and projects you authorize, and expect usage to count against Upstash billing.

Installation

In SourceWeft

  1. Open Upstash in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.upstash%2Fupstash-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "upstash": {
      "type": "http",
      "url": "https://mcp.upstash.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 23, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.