deno

This MCP server enables execution of Deno TypeScript and JavaScript code through an integrated MCP gateway. It exposes tools that let an LLM (such as Claude or Cline) request code execution, check the Deno version, and control permissions for the running code. The primary tool is execute_deno_code, which accepts code, a set of permissions (e.g., net, read, write, env, run), and optional flags for unstable features and TypeScript mode. You can also query check_deno_version to confirm the Deno runtime environment that the server is using. Use cases include running sandboxed Deno scripts, performing small system interactions with explicit permission grants, or prototyping Deno-based logic within a controlled context. The server enforces permission boundaries you specify per request, so you can run code that interacts with network, file system, environment variables, or subprocesses only when allowed.

Prerequisites:

• Node.js 16 or higher installed
• Deno installed (for runtime or testing Deno-specific features)
• Claude Desktop or Cline installed for MCP integration

Installation steps:

1. Clone the repository:

git clone https://github.com/Timtech4u/deno-mcp.git
cd deno-mcp

2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Ensure the built dist/index.js path matches your environment and update the MCP config accordingly (see mcp_config in this document).

Tips and notes:

• The MCP config uses a Node-based runner that executes the built index.js. Replace /absolute/path/to/deno-mcp/dist/index.js with your actual path after cloning and building.
• You can control permissions via the execute_deno_code tool by passing a permissions array, e.g., ["net", "read", "write"].
• The server defaults to a 30-second execution timeout for code runs; if your Deno code needs more time, consider adjusting the timeout settings if supported by your setup.
• If you see Deno-related errors, ensure Deno is installed and that the system PATH includes deno wherever the code or tests rely on it.
• For Claude Desktop and Cline, ensure you replace the absolute path in the config with the actual deployment path and restart the client after changes.