Log inSubmit server
MCP Server Js logo

MCP Server Js

by yepcode

Runs JavaScript or Python in YepCode’s sandbox and exposes YepCode processes as configurable MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Server Js

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "yepcode-mcp-server-js": {
      "command": "npx",
      "args": [
        "-y",
        "@yepcode/mcp-server"
      ],
      "env": {
        "YEPCODE_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @yepcode/mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 24d ago.

Overview

Run JavaScript or Python securely in YepCode with the yepcode/mcp-server-js MCP server, or expose tagged YepCode processes as agent-callable tools. It connects to YepCode through an API token and can be launched with NPX or Docker, with JSON Schema-based parameters for process tools. Reach for it when an MCP client needs sandboxed code execution, YepCode workflow access, or tools implemented across Node.js and Python.

Use cases

  • Execute generated JavaScript or Python in a YepCode sandbox
  • Expose tagged YepCode processes as MCP tools
  • Manage YepCode workspace variables and stored files
  • Enable process and execution management through MCP
  • Debug a local stdio server with MCP Inspector

Key features

  • Sandboxed JavaScript and Python execution
  • Tagged YepCode process exposure
  • JSON Schema parameters for process tools
  • Selective built-in and API tool loading
  • Workspace environment-variable management
  • NPX and Docker deployment

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

18/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @yepcode/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars47Stargazers on the source repository.
npm downloads138Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server Js works

What yepcode/mcp-server-js MCP server does

The yepcode/mcp-server-js MCP server connects an MCP-compatible AI platform to YepCode’s infrastructure. Its primary code-execution tool, run_code, sends JavaScript or Python to YepCode’s isolated environment and returns the execution result, console logs, or an error. Execution options can include the language, a comment describing the context, and runtime settings.

YepCode processes can also become MCP tools. Processes selected by tag are exposed individually, allowing a workspace to publish workflows with their own inputs and JSON Schema definitions. These tools can use OAuth, API tokens, or existing YepCode credentials according to the workspace’s security model. A single server can expose processes implemented in Node.js, Python, or both.

The server also supports YepCode management capabilities. Depending on configuration, these include process, schedule, variable, storage, execution, and module operations, along with version-management tools in the full API set.

How it works

The yepcode/mcp-server-js MCP server runs locally or in infrastructure you control and communicates with the MCP client over its configured transport. YepCode provides a hosted endpoint at https://cloud.yepcode.io/mcp for accounts that use the hosted service instead.

Tool exposure is controlled with YEPCODE_MCP_TOOLS. Built-in selections include run_code, yc_api, and yc_api_full; individual API tool names can also be selected. Adding a process tag exposes every matching process as an MCP tool. If this variable is omitted, built-in tools are enabled by default, while tagged process tools are not exposed.

YEPCODE_MCP_OPTIONS accepts comma-separated options. runCodeCleanup controls whether source created for run_code is removed after execution, and skipCodingRules omits the JavaScript and Python guidance included in the run_code schema.

Setup and configuration

Create a YepCode API token under the account’s API credentials settings, then provide it as YEPCODE_API_TOKEN. With Node.js 18 or later installed, an MCP client can launch the package through NPX using npx -y @yepcode/mcp-server. Docker users can build the repository image and pass the token into the container as an environment variable.

Cursor and Claude Desktop are named as supported integration targets in the README. For stdio troubleshooting, the project recommends the MCP Inspector, which can be started with npm run inspector and accessed in a browser.

Tools and capabilities

The yepcode/mcp-server-js MCP server documents these tool groups and operations:

  • run_code: execute code and receive a return value, logs, or an error.
  • set_env_var and remove_env_var: manage workspace environment variables; values can be marked sensitive when set.
  • list_files: list files in YepCode storage. The storage system also supports uploading, downloading, and deleting files for use by executions.
  • API management tools for processes, schedules, variables, storage, executions, and modules.
  • Process tools selected by tags, named from the process slug or, for long names, a generated name using the process ID.

The project description also identifies NPM and PyPI package support for generated JavaScript and Python code. Exact available packages and runtime limits are determined by the YepCode environment rather than by the MCP configuration shown here.

Limitations and notes

An API token is required for the documented local NPX or Docker setup. The server delegates execution and workspace operations to YepCode, so access, credentials, process configuration, and security behavior depend on the connected YepCode account.

Leaving YEPCODE_MCP_TOOLS unset exposes built-in tools but does not publish tagged processes. Selecting yc_api_full extends the basic API set with version-related process and module tools. Source cleanup is enabled by default for run_code; use the documented option when retaining source for audit purposes is required.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server Js

yepcode/mcp-server-js is an MCP server that connects AI platforms to YepCode. Its main tools execute JavaScript or Python in YepCode’s secure environment, manage workspace resources, and expose tagged YepCode processes as callable MCP tools with JSON Schema parameters.

Install it through NPX or Docker. NPX requires Node.js 18 or newer and runs `npx -y @yepcode/mcp-server`; Docker users can build the repository image. Both setups require a YepCode API token supplied as `YEPCODE_API_TOKEN`.

Yes, Cursor is named as an integration target. Configure Cursor to launch the server with NPX or Docker and provide `YEPCODE_API_TOKEN`; the README also identifies Claude Desktop as a supported client.

Set `YEPCODE_MCP_TOOLS` to one or more process tags. Every YepCode process with a selected tag is exposed as an individual MCP tool, using its JSON Schema parameter definition; built-in tools can be selected in the same variable.

Related MCP servers

All in Code Execution All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server Js AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/yepcode-mcp-server-js?style=directory)](https://allmcps.com/mcp/yepcode-mcp-server-js)
HTML Embed
<a href="https://allmcps.com/mcp/yepcode-mcp-server-js"><img src="https://allmcps.com/api/badge/yepcode-mcp-server-js?style=directory" alt="MCP Server Js on AllMCPs" /></a>