What are the prerequisites?
Docker must be installed and running on your machine. Pre‑pulling images like `node:lts-slim` is recommended to avoid delays.
@alfonsograziano
Basic information
A Node.js–based Model Context Protocol server that spins up disposable Docker containers to execute arbitrary JavaScript.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"js-sandbox": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-v",
"/var/run/docker.sock:/var/run/docker.sock",
"-v",
"$HOME/Desktop/sandbox-output:/root",
"-e",
"FILES_DIR=$HOME/Desktop/sandbox-output",
"alfonsograziano/node-code-sandbox-mcp"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
It is a Node.js server implementing the Model Context Protocol (MCP) for running arbitrary JavaScript in ephemeral Docker containers with on‑the‑fly npm dependency installation. It is for developers and AI agents who need an isolated, sandboxed JavaScript execution environment.
Install and run via Docker or npx, then configure your MCP client (e.g., Claude Desktop, VS Code) with the provided JSON config. Pass environment variables like FILES_DIR, SANDBOX_MEMORY_LIMIT, and SANDBOX_CPU_LIMIT. Use tools such as run_js_ephemeral for one‑off scripts or sandbox_initialize → run_js → sandbox_stop for session‑based workflows.
Docker must be installed and running on your machine. Pre‑pulling images like `node:lts-slim` is recommended to avoid delays.
Save files during script execution in the container’s working directory. Images (PNG, JPEG) are returned as image content; other files (e.g., .txt, .json) are returned as resource content. This feature is available only in the `run_js_ephemeral` tool.
Detached mode keeps the container alive after script execution, allowing long‑running services (e.g., servers) to stay active in the background. Use `run_js` with the `listenOnPort` parameter.
Set environment variables `SANDBOX_MEMORY_LIMIT` (e.g., `512m`) and `SANDBOX_CPU_LIMIT` (e.g., `0.5`) when launching the server.
Yes. The `image` parameter in tools like `run_js_ephemeral` and `sandbox_initialize` accepts any Docker image (default is `node:lts-slim`).
Quarkus LangChain4J Workshop that demonstrates both single AI service capabilities and Agentic AI orchestration
This project demonstrates a decoupled real-time agent architecture that connects LangGraph agents to remote tools served by custom MCP (Modular Command Protocol) servers. The architecture enables a flexible and scalable multi-agent system where each tool can be hosted independent
MCP server that allow LLM in agent mode builds n8n workflows for you
Agentic SWMM is an automated, auditable, and memory-informed framework for reproducible stormwater modelling, integrating QGIS and EPA SWMM through the aiswmm runtime, reusable Skills, and MCP interfaces, with QA verification, provenance tracking, calibration support, and Codex,
MCP Server for Agentic RAG applications
Comments