Add the Upstash MCP server to Cursor

{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/mcp-server"
      ],
      "env": {
        "UPSTASH_EMAIL": "<your UPSTASH_EMAIL>",
        "UPSTASH_API_KEY": "<your UPSTASH_API_KEY>"
      }
    }
  }
}

Scopes, env vars, OAuth and limits: Cursor MCP config guide

Cursor prompts you to sign in the first time a remote OAuth server is used. Upstash runs locally and needs UPSTASH_EMAIL, UPSTASH_API_KEY. Replace the placeholder values above with your own before starting Cursor.

Ask Cursor for something Upstash can do. Manage Upstash Redis, QStash and other Upstash resources through the Upstash Developer API. Approve the first tool call and check the result before allowing write actions automatically.

• · Remote servers take a url; local servers take command and args.
• · Values can reference ${env:NAME} so secrets stay out of the file.

How do I add the Upstash MCP server to Cursor?

Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.

Is this the official Upstash MCP server?

Yes. It is published by Upstash as io.github.upstash/mcp-server in the official MCP registry.

Does the Upstash MCP server need an API key?

Yes. It runs locally and requires UPSTASH_EMAIL, UPSTASH_API_KEY.