Deno MCP Server

Created By
Timtech4ua year ago
Overview

what is Deno MCP Server?

Deno MCP Server is a Model Context Protocol (MCP) server designed for executing Deno TypeScript and JavaScript code securely with configurable permissions, enabling LLMs like Claude to run Deno code.

how to use Deno MCP Server?

To use the Deno MCP Server, clone the repository, install dependencies, build the project, and configure it with either Claude Desktop or Cline. Once configured, you can ask Claude to run Deno code with specified permissions.

key features of Deno MCP Server?

  • Execute Deno TypeScript or JavaScript code
  • Configure permissions (net, read, write, env, run, etc.)
  • Enable/disable unstable features
  • Retrieve Deno version information

use cases of Deno MCP Server?

  1. Running Deno code with network permissions for API calls.
  2. Executing file system operations like reading and writing files.
  3. Utilizing Deno's standard library for server functionalities.

FAQ from Deno MCP Server?

  • What are the prerequisites for using Deno MCP Server?

You need Node.js 16 or higher, Deno installed, and either Claude Desktop or Cline.

  • How do I configure permissions?

Permissions can be configured in the respective configuration files for Claude Desktop or Cline.

  • What should I do if I encounter permission errors?

Ensure you are requesting the appropriate permissions for your code execution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Timtech4u
Star
0
Language
JavaScript
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