Tool reference

Execute JavaScript or Python in YepCode’s secure environment. Enable via YEPCODE_MCP_TOOLS=run_code.

Input: { code: string; options?: { language?: 'javascript'|'python'; comment?: string; settings?: object } }
Response: { returnValue?: unknown; logs?: string[]; error?: string }

Code runs in an isolated sandbox. Subject to plans and limits.

---

set_env_var: { key: string; value: string; isSensitive?: boolean } — isSensitive defaults to true (masked in logs)
remove_env_var: { key: string }

---

Uses YepCode Storage. Input/response schemas as in the README. Supports text and base64 binary. list_files accepts optional prefix.

---

Process tools: tag with mcp-tool (auto-exposed) or custom tags (add to YEPCODE_MCP_TOOLS). See Configuration.

Input: { parameters?: any; options?: { tag?: string; comment?: string }; synchronousExecution?: boolean }
Sync response: { executionId, logs, returnValue?, error? }
Async response: { executionId }

Define a clear JSON Schema for process inputs so the AI can call correctly.

---

Enable via YEPCODE_MCP_TOOLS=yc_api or yc_api_full (adds version management).

yc_api	yc_api_full adds
Processes, schedules, variables, storage, executions, modules	Process/module versions

Examples: get_processes, execute_process_sync, get_execution, etc. Full list and payloads: REST API Reference.