ai.getvda/redis-minio-postgres-stack-generator vs io.github.upstash/redis-mcp
ai.getvda/redis-minio-postgres-stack-generator is an MCP server published by getvda.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.upstash/redis-mcp is an MCP server published by upstash. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.upstash/redis-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (npm): 290 Downloads/week (npm): 71 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ai.getvda/redis-minio-postgres-stack-generator | io.github.upstash/redis-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (redis-minio-postgres-stack-generator.getvda.ai/mcp) | On your machine (@upstash/redis-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/upstash/redis-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-26 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ai.getvda/redis-minio-postgres-stack-generator
Redis + MinIO + Postgres Stack Generator
io.github.upstash/redis-mcp
Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP.
How to run each
ai.getvda/redis-minio-postgres-stack-generator As a remote MCP server
claude mcp add --transport http redis-minio-postgres-stack-generator https://redis-minio-postgres-stack-generator.getvda.ai/mcpio.github.upstash/redis-mcp As a local MCP server: npm package
claude mcp add --env "UPSTASH_REDIS_REST_TOKEN=<YOUR_UPSTASH_REDIS_REST_TOKEN>" --env "UPSTASH_REDIS_TCP_URL=<YOUR_UPSTASH_REDIS_TCP_URL>" --transport stdio redis-mcp -- npx -y @upstash/redis-mcpRequires: UPSTASH_REDIS_REST_TOKEN (secret), UPSTASH_REDIS_TCP_URL (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ai.getvda/redis-minio-postgres-stack-generator has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of ai.getvda/redis-minio-postgres-stack-generator publish no settings it asks for, so we do not compare settings.
What it can do: ai.getvda/redis-minio-postgres-stack-generator · What it can do: io.github.upstash/redis-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.