run_codeLABSCO SUMMARY
Your processes become the toolset, and unplanned code still runs safely.
Most servers ship a fixed tool list; here it is whichever processes you tagged, each with a schema you wrote, Python and Node.js side by side. run_code covers the rest: when a job needs glue nobody built a process for, the model writes it and YepCode runs it where your secrets already live.
What it is
YepCode's server, which exposes the processes in your workspace as callable tools and adds a sandbox where an agent can execute JavaScript or Python it just wrote.
What you get
- run_code, which executes JavaScript or Python in YepCode's isolated environment and returns the value, the logs, or the error
- Your own processes as tools: tag one mcp-tool and it appears immediately, or use custom tags and list them in YEPCODE_MCP_TOOLS
- A JSON Schema per process, so the model gets types, required fields, enums and defaults instead of guessing at inputs
- Storage tools — list_files, upload_file, download_file, delete_file — handling text and base64 binary across a multi-step task
- Environment variables through set_env_var and remove_env_var, sensitive by default and masked in logs
- API management through yc_api, or yc_api_full for version management, covering processes, schedules, variables, storage, executions and modules
- Processes run synchronously or asynchronously, returning an execution id either way
- Python and Node.js tools living in the same server rather than split across two
Requirements
A YepCode account. The hosted endpoint is https://cloud.yepcode.io/mcp and takes either OAuth or a token from Settings → API Credentials, passed in the URL or as an Authorization: Bearer header. Self-hosting needs Node.js 18 or later and a YEPCODE_API_TOKEN, run through NPX or Docker.
Setup effort
One command plus a key — npx -y @yepcode/mcp-server, then supply credentials
USE CASES
01
Exposing an internal automation to your assistant
Tag the process mcp-tool and give it a JSON Schema; it shows up as a tool the model can call correctly first try.
02
Running a piece of throwaway glue code safely
Let the model write the script and execute it in the sandbox, returning the value and the logs rather than a guess.
03
Carrying files between steps of a long task
Upload the intermediate artifact, list what is there, and pull it back down at the step that needs it.
04
Giving a tool a credential without pasting it into the chat
Set it as a sensitive environment variable so it is masked in logs, and remove it when the work is done.
05
Managing the workspace from the same conversation
List processes, start one, and read the execution back without leaving the client.
43 tools
Listed in project docs. Your client may show a different list.
set_env_varremove_env_varlist_filesupload_filedownload_filedelete_fileget_processescreate_processget_processupdate_processdelete_processget_process_versionsexecute_process_asyncexecute_process_syncschedule_processget_schedulesget_schedulepause_scheduleresume_scheduledelete_scheduleupdate_scheduleget_variablescreate_variableupdate_variabledelete_variableget_storage_objectsupload_storage_objectdownload_storage_objectdelete_storage_objectget_executionsget_executionkill_executionrerun_executionget_execution_logsget_modulescreate_moduleget_moduledelete_moduleget_module_versionsget_module_versiondelete_module_versionget_module_aliasesBEFORE YOU INSTALL
What to know first
Tools you get
43 tools named in the project's documentation.
Requires
- npx on PATH
- YEPCODE_API_TOKEN in your environment
Where it runs
Of the 4 documented setups, 2 run the server on your machine and 2 connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx -y @yepcode/mcp-serverHosted endpoint
ENDPOINT URL
https://cloud.yepcode.io/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Cursor — token URL
CURSOR — TOKEN URL · JSON
{
"mcpServers": {
"yepcode-mcp-server": {
"url": "https://cloud.yepcode.io/mcp/<YOUR_YEPCODE_TOKEN>"
}
}
}Any MCP client — auth header
ANY MCP CLIENT — AUTH HEADER · JSON
{
"mcpServers": {
"yepcode-mcp-server": {
"url": "https://cloud.yepcode.io/mcp",
"headers": {
"Authorization": "Bearer <YOUR_YEPCODE_TOKEN>"
}
}
}
}Cursor — npx, Claude Desktop — npx
JSON
{
"mcpServers": {
"yepcode-mcp-server": {
"command": "npx",
"args": [
"-y",
"@yepcode/mcp-server"
],
"env": {
"YEPCODE_API_TOKEN": "<YOUR_YEPCODE_API_TOKEN>"
}
}
}
}
