Deno KV

Provides an MCP interface for DenoKV enabling clients to read and write KV data through a simple local process.

typescript

5

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "littledivy-mcp-deno-kv": {
      "command": "deno",
      "args": [
        "--unstable-kv",
        "jsr:@divy/mcp-deno-kv"
      ]
    }
  }
}

This MCP server lets you interact with DenoKV data through a lightweight, configurable bridge. It enables MCP clients to store, retrieve, and manage key-value data backed by DenoKV, using a simple local process that you run on your machine or server.

How to use

You connect to this MCP server from an MCP client to perform standard data operations against DenoKV. Run the server with the provided runtime command, and then point your client at the local process. The server exposes a simple, stable interface suitable for typical KV use cases like storing session data, configuration flags, or lightweight caches. If you’re building an application that needs fast KV access with DenoKV at the core, this MCP server provides a clean integration point.

How to install

Prerequisites: ensure you have Deno installed on your system.

Install and run the MCP server using the runtime command shown in the configuration snippet.

Start the server with the command below. This runs Deno with the unstable key-value feature and loads the MCP bridge package.

deno --unstable-kv jsr:@divy/mcp-deno-kv

Additional notes

The server is designed to be run as a local, standalone process. If you are integrating this into a larger deployment, you can start it as part of your service startup sequence and ensure your MCP clients point to the same host/port where this process is available.

Configuration and troubleshooting

Configuration is determined by the command and arguments you run. The provided example uses the deno runtime with the unstable KV feature and loads the MCP bridge package, which enables MCP-style interactions with DenoKV.