What is Upstash MCP Server for managing context between LLMs and external systems.?
Model Context Protocol (MCP) is a new, standardized protocol for managing context between large language models (LLMs) and external systems. This repository provides an installer and an MCP Server for Upstash Developer API's, allowing interaction with Upstash accounts using natural language.
Documentation
Upstash MCP Server
Model Context Protocol (MCP) is a new, standardized protocol for managing context between large language models (LLMs) and external systems. In this repository, we provide an installer as well as an MCP Server for Upstash Developer API's.
This allows you to use any MCP Client to interact with your Upstash account using natural language, e.g.:
"Create a new Redis database in us-east-1"
"List my databases"
"List keys starting with "user:" in users-db"
"Create a backup"
"Give me the spikes in throughput during the last 7 days"
Add the following command to the MCP config in Windsurf. For more info, check out the Windsurf MCP docs.
npx -y @upstash/mcp-server run <UPSTASH_EMAIL> <UPSTASH_API_KEY>
Running with Docker
You can also use the provided Docker image to run the server.
docker build -t upstash-mcp .
# Run the stdio server, add this command to you MCP config
docker run --rm -i \
- e UPSTASH_EMAIL=<UPSTASH_EMAIL> \
- e UPSTASH_API_KEY=<UPSTASH_API_KEY> \
upstash-mcp
Troubleshooting## Common Issues
Your mcp client might have trouble finding the right binaries because of the differences between your shell and system PATH.
To fix this, you can get the full path of the binaries by running which npx or which docker in your shell, and replace the npx or docker command in the MCP config with the full binary path.
Node Version Manager
If you are using a node version manager like nvm or fnm, please check this issue. You should change the node command in the MCP config to the absolute path of the node binary.