DenoKV MCP Server

Created By
joshuayoesa year ago
An MCP Server for chatting with Deno KV instances
Overview

what is DenoKV MCP Server?

DenoKV MCP Server is a server designed for interacting with Deno KV instances, allowing users to chat and manage key-value pairs in a Deno environment.

how to use DenoKV MCP Server?

To use the DenoKV MCP Server, configure your MCP client (like Claude Desktop or Cursor) with the provided JSON configuration, specifying the command and environment variables needed to connect to your Deno KV database.

key features of DenoKV MCP Server?

  • Integration with Deno and Node.js for seamless key-value management.
  • Support for multiple commands like set, get, delete, and list for managing key-value pairs.
  • Environment variable configuration for local and remote database connections.

use cases of DenoKV MCP Server?

  1. Managing user sessions in a web application.
  2. Storing and retrieving application settings dynamically.
  3. Implementing caching mechanisms for improved performance.

FAQ from DenoKV MCP Server?

  • Can I use DenoKV MCP Server with Node.js?

Yes! DenoKV MCP Server can be used with Node.js through a compatibility layer.

  • What environment variables do I need to set?

You need to set DENO_KV_PATH for the database path and DENO_KV_ACCESS_TOKEN for remote databases.

  • Is there a way to run the server locally?

Yes! You can run the server locally by cloning the repository and using the provided configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
joshuayoes
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
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
Crevio

2 days ago