dicedb

DiceDB MCP implements a lightweight bridge between MCP clients and a DiceDB database using the DiceDB Go SDK. It exposes a set of standard MCP tools—ping, echo, get, set, del, incr, and decr—that let hosts and agents verify connectivity and perform basic CRUD-like operations on DiceDB keys. To use it, run the dicedb-mcp server and point your MCP clients at its address. Clients can then invoke the available tools to ping the DiceDB instance, echo messages, retrieve values by key, store key-value pairs, delete keys, or adjust numeric values atomically. This makes it convenient to incorporate DiceDB-backed state into AI workflows, prompts, or agents via the MCP interface.

Prerequisites:\n- Go 1.24 or higher (for building from source)\n- A DiceDB server to connect to (local or remote)\n\n1) Download the prebuilt binary:\n - Visit the releases page and download the appropriate dicedb-mcp binary for your OS/arch.\n\n2) Install via Go (from source):\nbash\ngo install github.com/pottekkat/dicedb-mcp@latest\n\n\n3) Verify the binary is installed:\nbash\nwhich dicedb-mcp\n\n\n4) Build from source (optional):\nbash\ngit clone https://github.com/pottekkat/dicedb-mcp.git\ncd dicedb-mcp\nmake deps\nmake build\n\n\n5) Run the server (example):\nbash\ndicedb-mcp\n\n

Tips and notes:\n- Ensure your DiceDB server is reachable by the MCP server and that any network/firewall settings permit the connection.\n- The server exposes a minimal set of tools (ping, echo, get, set, del, incr, decr). Use the appropriate MCP client configuration to invoke these tools.\n- If you deploy from source, you can adjust the command path in your MCP host config to point to the built binary.\n- For development, you can verify connectivity with the ping tool before attempting get/set operations.\n- When using incr/decr, ensure the target key holds an integer value to avoid errors.