Supports containerized deployment, allowing AI systems to run YepCode processes in isolated Docker environments.
Integration with GitHub workflows for CI/CD, as indicated by the GitHub Workflow Status badge.
Enables execution of JavaScript code in YepCode's secure environment, with support for process management and environment variables.
Allows deployment and execution through NPX, enabling AI assistants to run YepCode processes and interact with npm packages.
Supports TypeScript code execution through YepCode's infrastructure, allowing AI assistants to run type-safe scripts.
What is YepCode MCP Server?
An MCP (Model Context Protocol) server that enables AI platforms to interact with YepCode's infrastructure. Run LLM generated scripts and turn your YepCode processes into powerful tools that AI assistants can use directly.
Why YepCode MCP Server?
- Seamless AI Integration: Convert YepCode processes into AI-ready tools with zero configuration
- Real-time Process Control: Enable direct interaction between AI systems and your workflows
- Enterprise-Grade Security: Execute code in YepCode's isolated, production-ready environments
- Universal Compatibility: Integrate with any AI platform supporting the Model Context Protocol
Integration Guide
YepCode MCP server can be integrated with AI platforms like Cursor or Claude Desktop using either a remote approach (we offer a hosted version of the MCP server) or a local approach (NPX or Docker installation is required).
For both approaches, you need to get your YepCode API credentials:
- Sign up to YepCode Cloud
- Visit
Settings
>API credentials
to create a new API token.
Remote Approach using SSE Server
- If your MCP Client doesn't support authentication headers, just use the SSE server URL that includes the API Token. Use a configuration similar to the following:
- If your MCP Client supports authentication headers, you can use the HTTP server URL that includes the API Token. Use a configuration similar to the following:
Local Approach
Using NPX
Make sure you have Node.js installed (version 18 or higher), and use a configuration similar to the following:
Using Docker
- Build the container image:
- Use a configuration similar to the following:
Debugging
Debugging MCP servers can be tricky since they communicate over stdio. To make this easier, we recommend using the MCP Inspector, which you can run with the following command:
This will start a server where you can access debugging tools directly in your browser.
YepCode MCP Tools Reference
The MCP server provides several tools to interact with YepCode's infrastructure:
Code Execution
run_code
Executes code in YepCode's secure environment.
MCP Options
YepCode MCP server supports the following options:
- Disable the run_code tool: In some cases, you may want to disable the
run_code
tool. For example, if you want to use the MCP server as a provider only for the existing tools in your YepCode account. - Skip the run_code cleanup: By default, run_code processes source code is removed after execution. If you want to keep it for audit purposes, you can use this option.
Options can be passed as a comma-separated list in the YEPCODE_MCP_OPTIONS
environment variable or as a query parameter in the MCP server URL.
Environment Management
set_env_var
Sets an environment variable in the YepCode workspace.
remove_env_var
Removes an environment variable from the YepCode workspace.
Storage Management
YepCode provides a built-in storage system that allows you to upload, list, download, and delete files. These files can be accessed from your code executions using the yepcode.storage
helper methods.
list_files
Lists all files in your YepCode storage.
upload_file
Uploads a file to YepCode storage.
download_file
Downloads a file from YepCode storage.
delete_file
Deletes a file from YepCode storage.
Process Execution
The MCP server can expose your YepCode Processes as individual MCP tools, making them directly accessible to AI assistants. This feature is enabled by just adding the mcp-tool
tag to your process (see our docs to learn more about process tags).
There will be a tool for each exposed process: run_ycp_<process_slug>
(or run_ycp_<process_id>
if tool name is longer than 60 characters).
run_ycp_
get_execution
Retrieves the result of a process execution.
License
This project is licensed under the MIT License - see the LICENSE file for details.
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
An MCP server that enables AI platforms to interact with YepCode's infrastructure, allowing LLM-generated scripts to run on YepCode and turning YepCode processes into powerful tools that AI assistants can use directly.
Related MCP Servers
- AsecurityAlicenseAqualityA Model Context Protocol server that enables AI assistants to interact with Linear project management systems, allowing users to retrieve, create, and update issues, projects, and teams through natural language.Last updated -421,070101MIT License
- AsecurityFlicenseAqualityAn MCP server that supercharges AI assistants with powerful tools for software development, enabling research, planning, code generation, and project scaffolding through natural language interaction.Last updated -1114272
- AsecurityAlicenseAqualityA Model Context Protocol (MCP) server for LeetCode that enables AI assistants to access LeetCode problems, user information, and contest data.Last updated -7724MIT License
- -securityAlicense-qualityA Code Indexing MCP Server that connects AI coding assistants to external codebases, providing accurate and up-to-date code snippets to reduce mistakes and hallucinations.Last updated -77Apache 2.0