Redis MCP Server by CData

Created By
CDataSoftwarea year ago
This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free [CData MCP Server for Redis (beta)](https://www.cdata.com/download/download.aspx?sku=EIZK-V&type=beta).
Overview

What is Redis MCP Server by CData?

Redis MCP Server by CData is a read-only Model Context Protocol (MCP) server that allows large language models (LLMs) to query live data from Redis without needing SQL. It is designed to work with the CData JDBC Driver for Redis, exposing Redis data as relational SQL models.

How to use Redis MCP Server?

To use the Redis MCP Server, clone the repository, build the server, install the CData JDBC Driver, configure your connection, and create a configuration file for your AI client (e.g., Claude Desktop). Finally, run the server and interact with it using natural language queries.

Key features of Redis MCP Server?

  • Read-only access to Redis data through a simple MCP interface.
  • No SQL required for querying data.
  • Integration with LLMs for natural language queries.
  • Supports various data sources through the CData JDBC Driver.

Use cases of Redis MCP Server?

  1. Querying live data from Redis using natural language.
  2. Integrating with AI clients for enhanced data interaction.
  3. Simplifying data access for applications that require real-time information.

FAQ from Redis MCP Server?

  • Can I write data to Redis using this server?

No, this server is read-only. For write capabilities, consider the full CData MCP Server for Redis.

  • Is there a trial version available?

Yes, you can download a beta version of the full CData MCP Server for Redis for free.

  • What kind of queries can I run?

You can ask natural language questions about your data, such as "What is the correlation between my closed won opportunities and the account industry?"

Server Config

{
  "mcpServers": {
    "{classname_dash}": {
      "command": "PATH\\TO\\java.exe",
      "args": [
        "-jar",
        "PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
        "PATH\\TO\\redis.prp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CDataSoftware
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago