Can I use Upstash Redis as a CLI?

Yes. KosmoKrator exposes a Upstash Redis CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Upstash Redis through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Upstash Redis tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Upstash Redis credentials stored?

Upstash Redis credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Upstash Redis MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

data

Upstash Redis MCP Integration for Generic MCP Clients

Connect Upstash Redis to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 5 read 2 write API key auth

Submit Upstash Redis feedback View package source

Connect Upstash Redis to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

Register kosmo mcp:serve as the command for a local stdio MCP server. The gateway is local, scoped to this integration, and starts with --write=deny so MCP clients can inspect read-capable tools without receiving write access by default.

Upstash Redis MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

{
  "mcpServers": {
    "kosmokrator-upstash": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=upstash",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=upstash --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Upstash Redis instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Upstash Redis Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the Upstash Redis integration catalog.

MCP tool	Source function	Type	Description
`integration__upstash__upstash_get_key`	`upstash.upstash_get_key`	Read	Retrieve the value stored at a Redis key. Returns null if the key does not exist.
`integration__upstash__upstash_set_key`	`upstash.upstash_set_key`	Write	Store a key-value pair in Redis. Optionally set a TTL (time-to-live) in seconds so the key expires automatically.
`integration__upstash__upstash_delete_key`	`upstash.upstash_delete_key`	Write	Delete a key from Redis. Returns the number of keys that were removed.
`integration__upstash__upstash_list_keys`	`upstash.upstash_list_keys`	Read	List Redis keys matching a glob-style pattern. Defaults to "*" to list all keys.
`integration__upstash__upstash_list_databases`	`upstash.upstash_list_databases`	Read	List all Redis databases in the Upstash account. Returns database IDs, names, regions, and endpoints.
`integration__upstash__upstash_get_database`	`upstash.upstash_get_database`	Read	Get details for a specific Upstash Redis database by ID, including endpoint, region, and usage stats.
`integration__upstash__upstash_get_current_user`	`upstash.upstash_get_current_user`	Read	Get current team information from Upstash, including team name, members, and plan details.

Related Upstash Redis Pages

Upstash Redis CLIUse direct JSON commands instead of MCP discovery. Upstash Redis MCPFull gateway reference and MCP tool names. KosmoKrator for MCP clientsClient-level gateway setup.