mcp

This MCP server integrates with Upstash Developer APIs to allow natural-language driven interaction with your Upstash resources. Using the included NPX-based start, you can launch the Upstash MCP server directly from the command line and connect it to your MCP client (e.g., Cursor, Claude Desktop, or VS Code). The server exposes a set of Redis-related tools and commands that let you create, list, back up, and manage Redis databases and keys through natural language prompts. Typical usage includes asking to list databases, create a new Redis database in a specific region, manage backups, or query usage and performance metrics. The README provides concrete examples for both starting the server with credentials and configuring MCP clients to point at the server, including an HTTP transport option for web apps.

To use the server in a client, configure your MCP client with the upstash server entry and supply your Upstash email and API key. You can also run the server via Docker or configure a transport (such as HTTP) to expose an endpoint for web applications. The tools section enumerates the Redis-related actions available (e.g., redis_database_create_new, redis_database_list_databases, redis_database_get_stats) so you know which operations you can invoke through natural language prompts.

Prerequisites:

• Node.js 18.x or newer
• An Upstash account with an API key
• Optional: Docker if you plan to run via container

Installation steps:

1. Install Node.js (if not already installed). Visit https://nodejs.org/ and install the LTS release for your platform.
2. Install or run the MCP server via NPX (as suggested by the README):

# Quick start without global install (recommended)
npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY

If you prefer a global install:

npm install -g @upstash/mcp-server
upstash-mcp-server --email YOUR_EMAIL --api-key YOUR_API_KEY

3. Alternatively, you can build and run via Docker (see Docker setup in README) by creating a Docker image from the provided Dockerfile and running it with the appropriate environment variables (UPSTASH_EMAIL, UPSTASH_API_KEY).
4. For client configuration, refer to the provided examples in the README to point your MCP client to the server (npx usage, HTTP transport, or Docker-based configuration).

Prerequisites recap:

• Node.js v18+ (or Docker as an alternative deployment path)
• Upstash API key
• Optional email for credential-based initialization

Tips and caveats:

• If your MCP client cannot locate binaries, use the full path for npx or docker as described in the troubleshooting section of the README.
• If using a Node version manager (nvm/fnm), you may need to use the absolute path to the node binary in your MCP client configuration.
• The README includes an HTTP transport option for web apps (transport http) and a sample client configuration pointing to http://localhost:3000/mcp.
• When using Docker, ensure the image tag matches the one you built and pass credentials via environment variables inside the container (e.g., UPSTASH_EMAIL, UPSTASH_API_KEY).
• The MCP Tools section lists commands like redis_database_create_new, redis_database_list_databases, redis_database_get_usage_last_5_days, etc. These are the building blocks for natural-language prompts.
• Logs can be monitored with pnpm run logs if you’re developing locally with PNPM.