Overview
Features
Secure Code Execution (run_code)
Executes code in YepCode's sandboxed environment with optional language, context, and runtime settings; returns a value, logs, and potential error. Supports runCodeCleanup option to keep or remove source after execution.
Expose Processes as MCP Tools
Transforms tagged YepCode processes into individual MCP tools, named after the process slug (or yc_ prefixed if long). Supports synchronous and asynchronous execution and exposure control via environment variables.
Environment Management
Manage workspace environment variables through set_env_var and remove_env_var operations, enabling dynamic configuration of executed code.
Storage Management
Built-in YepCode storage to list, upload, download, and delete files, accessible from code executions via yepcode.storage helpers.
Remote and Local Deployment
Flexible deployment options including a hosted remote SSE server or local deployment via NPX or Docker, with API token authentication.
API Management Tools
Access comprehensive API tooling via yc_api and yc_api_full for managing processes, schedules, variables, storage, executions, and modules.
Debugging Support
Debug MCP servers using the MCP Inspector, with a browser-accessible debugging server started via npm run inspector.
Real-time Process Control
Enable direct, real-time interaction between AI systems and YepCode workflows for dynamic, responsive automation.
Who Is This For?
- AI Platform Developers:Integrate YepCode processes as MCP tools in AI assistants with secure, scalable execution.
- Enterprise Teams:Run production-grade processes securely with logs, access control, and sandboxed environments.
- Developers adopting Model Context Protocol:Expose YepCode processes as MCP tools for browser-based or hosted AI integrations.




