YepCode
About
Execute any LLM-generated code in the [YepCode](https://yepcode.io) secure and scalable sandbox environment and create your own MCP tools using JavaScript or Python, with full support for NPM and PyPI packages
Details
- Author
- yepcode
- GitHub stars
- 44
- Downloads
- 332
- Categories
- Developer Tools, Automation, Infrastructure, Other
Jump to
- Expose YepCode processes as MCP tools with JSON Schema parameters
- Execute code securely in YepCode’s isolated environment via run_code
- Manage environment variables, storage files, and processes
- Polyglot tool implementations in Python or Node.js in one server
- Control which tools are enabled via YEPCODE_MCP_TOOLS (tags and categories)
- Enterprise-grade security with OAuth, API tokens, or workspace credentials
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
YepCodeCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Requires Node.js 18+ or Docker and a YepCode API token. Configure your AI client (e.g., Cursor, Claude Desktop) with the command npx -y @yepcode/mcp-server and the YEPCODE_API_TOKEN environment variable. Alternatively, use Docker with docker run. The hosted MCP server at https://cloud.yepcode.io/mcp requires no local installation.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"yepcode": {
"yepcode-mcp-server-stdio": {
"command": "npx",
"args": [
"-y",
"@yepcode/mcp-server"
],
"env": {
"YEPCODE_API_TOKEN": "your_api_token_here"
}
}
}
}
}
McpServers
{
"yepcode-mcp-server-stdio": {
"command": "npx",
"args": [
"-y",
"@yepcode/mcp-server"
],
"env": {
"YEPCODE_API_TOKEN": "your_api_token_here"
}
}
}
Yepcode-mcp-server-sse
{
"url": "https://cloud.yepcode.io/mcp/sk-c2E....RD/sse"
}
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. YepCode is the perfect environment to build a dynamic MCP tools server: expose each process as a tool (with OAuth, API tokens, or your credentials), define each tool's parameters with JSON Schema for full flexibility, and implement tools in Python or Node.js—all in one server that mixes multiple languages.
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
YepCode: The Perfect Environment for a Dynamic MCP Tools Server
YepCode is built to be the ideal platform for running a dynamic MCP tools server:
- One process, one tool: Each YepCode process can be exposed as an MCP tool. Tag your processes (e.g. mcp-tool, core, automation) and they become tools that AI assistants can invoke. You can secure access with OAuth, API tokens, or your existing YepCode credentials—each tool runs in your workspace with the same security model.
- Full control over tool parameters: Every tool can define its own parameter schema as JSON Schema. You get complete flexibility to describe inputs (types, descriptions, required fields, enums, defaults, etc.), so the AI receives rich metadata and can call your tools correctly.
- Polyglot tool implementations: Implement tools in Python or Node.js (or both). The same MCP server can expose tools backed by different runtimes—think of it as one MCP server that mixes implementations across several languages.
For complete documentation, see the YepCode MCP Server docs.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.


