Redis MCP Server

Created By
redisa year ago
The official Redis MCP Server is a natural language interface designed for agentic applications to manage and search data in Redis efficiently
Overview

What is Redis MCP Server?

The Redis MCP Server is a natural language interface designed for agentic applications to efficiently manage and search data in Redis, integrating seamlessly with MCP clients for AI-driven workflows.

How to use Redis MCP Server?

To use the Redis MCP Server, clone the repository, install dependencies, and configure the environment variables for Redis connection. You can then run the application to interact with Redis using natural language queries.

Key features of Redis MCP Server?

  • Natural Language Queries for data management.
  • Seamless integration with MCP clients.
  • Full support for Redis data structures including hashes, lists, sets, and streams.
  • Efficient search and filtering capabilities.
  • Scalable and lightweight design for high-performance operations.

Use cases of Redis MCP Server?

  1. AI Assistants for data fetching and processing.
  2. Chatbots managing session data and personalizing responses.
  3. Real-time data search and analytics.
  4. Event processing using Redis Streams.

FAQ from Redis MCP Server?

  • Can I use Redis MCP Server with any MCP client?

Yes! It is designed to work with any MCP client for smooth communication.

  • What programming language is Redis MCP Server written in?

The server is written in Python.

  • Is there a license for Redis MCP Server?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
redis
Star
72
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago