Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md to add Redis to Community Servers #586

Merged
merged 2 commits into from
Feb 10, 2025

Conversation

prajwalnayak7
Copy link
Contributor

@prajwalnayak7 prajwalnayak7 commented Feb 2, 2025

Description

This change introduces the Redis Model Context Protocol (MCP) server, enabling seamless interaction with Redis Server, AWS MemoryDB, and similar in-memory, key-value storage systems. The server facilitates efficient caching and other use-cases requiring fast, persistent data storage and retrieval. It provides a unified interface for managing various Redis-compatible backends, simplifying integration with Claude Desktop and other applications.

Server Details

  • Server: Redis MCP Server

Motivation and Context

The Redis MCP server was developed to streamline caching and data persistence operations across projects, offering an intuitive interface compatible with Claude Desktop. It addresses the critical need for maintaining simple data beyond individual LLM interactions, enhancing the overall user experience and system efficiency. This server enables the augmentation and restoration of additional context from different conversations or external sources, significantly improving the continuity and coherence of interactions. By providing a standardized approach to in-memory data management, the Redis MCP server reduces implementation complexity and promotes better scalability and performance in applications requiring rapid data access and storage.

How Has This Been Tested?

  1. Connection success/failure with redis server (local docker)
  2. Connection success/failure with redis server (AWS MemoryDB)
  3. Fetching the status resource
  4. Basic operations to get and set values
  5. List operations
  6. Hash operations
  7. Set operations
  8. List all tools & resources

Breaking Changes

NA

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Copy link
Contributor

@jerome3o-anthropic jerome3o-anthropic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just resolved some conflicts, thanks for the PR

@jerome3o-anthropic jerome3o-anthropic merged commit ebac6f2 into modelcontextprotocol:main Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants