MCP QuickJS Runner
Provides a secure environment to execute arbitrary JavaScript code inside a sandboxed QuickJS WASM environment, capturing standard output, standard error, and execution errors.
Utilizes Node.js's built-in WASI implementation to instantiate and run the QuickJS WASM module, enabling secure JavaScript code execution with captured I/O.
Leverages WebAssembly to create a secure sandbox for JavaScript code execution through a pre-compiled QuickJS engine targeting the WebAssembly System Interface (WASI).
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
MCP QuickJS Runner
A server implementing the Model Context Protocol (MCP) that provides a tool to securely execute arbitrary JavaScript code within a QuickJS engine compiled to WebAssembly (WASM) and run using Node.js's built-in WASI implementation.
Description
This server acts as an MCP tool provider. It exposes a single tool, run_javascript_code, which takes a string of JavaScript code as input. The code is then executed inside a sandboxed QuickJS WASM environment. The server captures the standard output (stdout) and standard error (stderr) streams from the execution and returns them, along with any execution errors, back to the MCP client.
This allows language models or other MCP clients to safely execute potentially untrusted JavaScript code snippets without compromising the host system.
Related MCP server: Node Code Sandbox MCP
Features
Secure Execution: Runs JavaScript in a WASM sandbox using QuickJS and Node.js WASI.
Standard I/O Capture: Captures
stdoutandstderrfrom the executed JavaScript code.Error Reporting: Reports runtime errors from QuickJS and non-zero exit codes.
MCP Integration: Exposes functionality as a standard MCP tool over
stdio.Built with TypeScript: Provides type safety during development.
How it Works
WASM Module: Uses a pre-compiled QuickJS engine (
qjs-wasi.wasm) targeting the WebAssembly System Interface (WASI).Node.js WASI: Leverages the
node:wasimodule in Node.js to instantiate and run the WASM module.Stdio Redirection (Temporary Files): To capture
stdoutandstderrfrom the WASM environment, the server currently relies on the standard approach compatible withnode:wasi:A temporary directory is created on the host filesystem using
node:fs/promisesandnode:os.Temporary files for
stdoutandstderrare opened within this directory.The real OS file descriptors for these files are passed to the
WASIinstance during initialization (stdout: fd,stderr: fd).The QuickJS WASM module writes its output to these descriptors, which gets routed by WASI to the temporary files.
After execution finishes, the server closes the file handles and reads the content of the temporary files.
The temporary directory and files are cleaned up.
(Note: Attempts to use in-memory pipes or virtual filesystems like
memfswere unsuccessful becausenode:wasicurrently requires real OS file descriptors for stdio.)
MCP Communication: The server uses
@modelcontextprotocol/sdkto listen for MCP requests viastdioand respond with the execution results formatted according to the protocol.
Prerequisites
Node.js (v23.x or later recommended, check
node:wasicompatibility for your specific version)The QuickJS WASM file (
qjs-wasi.wasm) must be present in the same directory as the compiled server script (e.g.,./dist/qjs-wasi.wasmrelative to./dist/server.js). You may need to obtain or compile this separately.
Installation
Clone the repository (if applicable).
Install dependencies:
npm install
Usage
node server.tsTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Secure Linux sandboxes for AI agents, as MCP tools.
Execute code in 8 languages (Python, JS, TS, Go, Java, C++, C, Bash) in gVisor sandboxes.
Execution platform for AI agents on Firecracker microVMs in the EU. Interactive Linux sandboxes with root, templates for Python, Node.js, Go, Rust and a headless browser, public HTTPS URLs. Background jobs that outlive the connection, batches of up to 1,000 jobs with dependencies, hard cost caps reserved up front, execution receipts with SHA-256, log digests that fit the context. IPv4, dual-stack or IPv6-only with its own public address, allowlists or no network. WASI runtime for small tasks. Idle sandboxes sleep and keep their files. Also REST API, Python SDK and LangChain.
Sandboxes, storage, secrets, queues, timers, locks, inboxes and run ledger for AI bots. One MCP.
Related MCP Servers
- FlicenseBqualityDmaintenanceProvides a secure, isolated JavaScript execution environment with configurable time and memory limits for safely running code from Claude.138 npm5-
- FlicenseAqualityDmaintenanceA secure Node.js execution environment that allows coding agents and LLMs to run JavaScript dynamically, install NPM packages, and retrieve results while adhering to the Model Control Protocol.7111 npm4-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with MCP servers by writing TypeScript/JavaScript code instead of direct tool calls. Provides a code execution sandbox that accesses MCP servers through HTTP proxy endpoints.19 npm131Apache 2.0
- FlicenseNot gradedqualityDmaintenanceExecutes TypeScript code in a secure sandbox with IPC-bridged access to MCP tools like filesystem operations and network requests.3-