What transport does Redis MCP Server use?
It uses SSE (Server-Sent Events) via the `spring-ai-mcp-server-webmvc-spring-boot-starter` module, making it suitable for web‑based MCP clients.
@yyue9527
Basic information
A Redis Management and Control Protocol (MCP) server implementation using Spring Boot and Spring AI
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Redis MCP Server is a Model Context Protocol (MCP) server that exposes Redis operations as MCP tools. Built with Spring Boot and Spring AI, it uses SSE (Server-Sent Events) transport to allow AI assistants and MCP clients to interact with a Redis database through standard key-value commands.
Prerequisites: JDK 17+, Maven 3.6+, and a running Redis server. Build with mvn clean package and run with java -jar target/redis-mcp-server-{version}.jar. Configure the Redis connection via the redis.url system property (default: redis://localhost:6379). The server exposes four MCP tools: set, get, delete, and list. For use in Cursor, add the tool configuration pointing to http://localhost:8080/sse.
It uses SSE (Server-Sent Events) via the `spring-ai-mcp-server-webmvc-spring-boot-starter` module, making it suitable for web‑based MCP clients.
JDK 17 or higher, Maven 3.6 or higher, and an accessible Redis server are required.
Set the `redis.url` system property to your Redis URI (e.g., `redis://your-host:6379`). The default value is `redis://localhost:6379`.
Add the following to your Cursor settings: a tool definition with `"url": "http://localhost:8080/sse"` and `"enabled": true`.
It provides four tools: `set` (key-value with optional expiry), `get`, `delete` (one or more keys), and `list` (pattern‑based key listing).
A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma
Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.
The Xata MCP server lets AI assistants and agents interact with your Xata organizations, projects, and Postgres database branches.
Universal MCP-Server for your Databases optimized for LLMs and AI-Agents.
Comments