Mcp Redis

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026

Read-only Redis for AI agents — keys, hashes, lists, sets, sorted sets, streams, INFO.

VerifiedSTDIODesktop onlyDatabases

Overview

AI-generated overview

A local, read-only Redis MCP server that lets an AI assistant inspect keys and common Redis data structures without modifying the database.

What you can do
Inspect Redis keys and look up their values and metadata across the main data types: hashes, lists, sets, sorted sets and streams. Read server status and statistics through INFO. All access is described as read-only, so the assistant can explore and report on stored data without writing to it.
When to use it
Useful when you want an assistant to explore or explain what is stored in a Redis instance, such as reviewing key layouts, sampling collections, or checking server status, without giving it write access.
Requirements
Runs as a local process on the user's machine via the npm package @infoinlet/mcp-redis over stdio, so Node.js and npm are needed. It must be able to reach the target Redis instance; no authentication, environment variables or headers are declared.
Before you install
The server is described as read-only, but it still connects to a live Redis database, so point it only at instances whose data the assistant is allowed to see. No credentials are declared, so access control depends on how the Redis instance itself is configured.

Installation

In SourceWeft

  1. Open Mcp Redis in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.