Mongodb MCP Server vs Redis MCP

A side-by-side look at the Mongodb MCP Server and Redis MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Mongodb MCP Server logoMongodb MCP ServerDatabases · Local subprocess (stdio)A Model Context Protocol server to connect to MongoDB databases and MongoDB Atlas Clusters.65GreatAuth: not declaredRedis MCP logoRedis MCPDatabases · Local subprocess (stdio)Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP.55GoodAuth: not declared

Verdict: choose Mongodb MCP Server for databases work as a local process; choose Redis MCP for databases as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Mongodb MCP Server logoChoose Mongodb MCP Server when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: MDB_MCP_CONNECTION_STRING.
  • You want tools like aggregate, aggregate-db, collection-indexes.
Explore Mongodb MCP Server

Redis MCP logoChoose Redis MCP when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN, UPSTASH_REDIS_TCP_URL, REDIS_URL.
  • You want tools like redis_run_commands, redis_search_docs.
Explore Redis MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMongodb MCP Server logoMongodb MCP ServerRedis MCP logoRedis MCP
CategoryDatabasesDatabases
Quality signal65/100 · Great55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsMDB_MCP_CONNECTION_STRINGUPSTASH_REDIS_REST_URLUPSTASH_REDIS_REST_TOKENUPSTASH_REDIS_TCP_URLREDIS_URL
Verified ownerCommunity listingCommunity listing
GitHub stars1,1500
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools532

Tools & capabilities

Mongodb MCP Server tools 53

  • aggregateRun an aggregation against a MongoDB collection
  • aggregate-dbRun an aggregation against a MongoDB database
  • collection-indexesDescribe the indexes for a collection
  • collection-schemaDescribe the schema for a collection
  • collection-storage-sizeGets the size of the collection
  • connectConnect to a MongoDB instance
  • countGets the number of documents in a MongoDB collection using db.collection.count() and query as an optional filter parameter
  • create-collectionCreates a new collection in a database. If the database doesn't exist, it will be created automatically.
  • create-indexCreate an index for a collection
  • db-statsReturns statistics that reflect the use state of a single database
  • delete-manyRemoves all documents that match the filter from a MongoDB collection
  • disconnectClose a MongoDB connection and revoke its connectionId.
  • +41 more on the listing page

Redis MCP tools 2

  • redis_run_commandsRun one or more Redis commands against an Upstash Redis database (this server is ONLY for Upstash Redis). Commands are sent over HTTP/REST or native TCP depending on how the target database is configured — you don't choose the transport. By default multiple commands run as a pipeline: each returns its own result/error, and one failure does not abort the others. Set transaction:true to run them atomically (MULTI/EXEC). For discovery prefer SCAN over KEYS, and use TYPE to inspect a key. A valid command that fails (e.g. WRONGTYPE) returns a per-command error while the rest of the pipeline still runs; a malformed/unknown command can cause the whole request to be rejected. Upstash Redis Search runs through THIS tool via SEARCH.* commands (SEARCH.LISTINDEXES/CREATE/QUERY/AGGREGATE/COUNT/DESCRIBE) — NOT RediSearch's FT.*; filters/aggregations are JSON strings. If you don't know the index name, run SEARCH.LISTINDEXES first; then SEARCH.DESCRIBE <index> for field names/types, and call redis_search_docs for syntax. Three gotchas: (1) a filter applies to ALL indexed documents unless you scope it, e.g. {"type":"story"} — an empty {} counts every type; (2) a plain text value like {"title":"x"} does fuzzy/smart matching, so for an exact word or adjacent phrase use {"title":{"$phrase":"x"}}; (3) add SELECT <n> field... to a query to return only the fields you need instead of whole documents.
  • redis_search_docsLook up **Upstash Redis** documentation — any command, feature, option, or syntax. Covers the whole Upstash Redis surface: core Redis commands, the REST API, pipelines/transactions, and Upstash-specific features. This INCLUDES Upstash Redis Search — the SEARCH.* full-text family (SEARCH.CREATE / SEARCH.QUERY / SEARCH.AGGREGATE / SEARCH.COUNT / ...), whose JSON-based index schema and query syntax are Upstash-specific and DIFFER from Redis Labs' RediSearch FT.*, so they are unlikely to be in your training data — verify them here. Reach for this whenever you're unsure about a command, option, or syntax, and ALWAYS before writing a SEARCH.* command. Pass a natural-language query.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Mongodb MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server@latest"
      ],
      "env": {
        "MDB_MCP_CONNECTION_STRING": "YOUR_MDB_MCP_CONNECTION_STRING_HERE"
      }
    }
  }
}

Redis MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "redis-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/redis-mcp"
      ],
      "env": {
        "UPSTASH_REDIS_REST_URL": "YOUR_UPSTASH_REDIS_REST_URL_HERE",
        "UPSTASH_REDIS_REST_TOKEN": "YOUR_UPSTASH_REDIS_REST_TOKEN_HERE",
        "UPSTASH_REDIS_TCP_URL": "YOUR_UPSTASH_REDIS_TCP_URL_HERE",
        "REDIS_URL": "YOUR_REDIS_URL_HERE"
      }
    }
  }
}

Frequently asked questions

Mongodb MCP Server is categorized under Databases and uses a local stdio subprocess. Redis MCP belongs to Databases and uses a local stdio subprocess. Pick Mongodb MCP Server for databases work and Redis MCP for databases.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Mongodb MCP Server has no declared pricing — check the project's own site. Redis MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mongodb-mcp-server and redis-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Mongodb MCP Server has a quality signal of 65/100 (Great) with 1 views, 0 installs and 1,150 GitHub stars. Redis MCP has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.