YepCode MCP Server

YepCode becomes available to MCP clients through the yepcode mcp server. Execute any LLM-generated code in the YepCode secure and scalable sandbox environment and create your own MCP tools using JavaScript or Python, with full support for NPM and PyPI packages.

What YepCode does

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.

Key capabilities

• 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

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• get_processes — List processes with optional filtering
• create_process — Create new processes with source code
• get_process — Get process details
• update_process — Update an existing process
• delete_process — Delete a process
• get_process_versions — Get process versions (requires yc_api_full)
• execute_process_async — Execute a process asynchronously
• execute_process_sync — Execute a process synchronously
• schedule_process — Schedule a process to run automatically
• get_schedules — List scheduled processes
• get_schedule — Get schedule details
• pause_schedule — Pause a scheduled process
• resume_schedule — Resume a paused schedule
• delete_schedule — Delete a schedule

Installing the yepcode mcp server

The server is distributed via npm as Make, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 3 environment variables: YEPCODE_API_TOKEN, YEPCODE_MCP_OPTIONS, YEPCODE_MCP_TOOLS. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

Get your YepCode API credentials: 1. Sign up to YepCode Cloud 2. Visit Settings > API credentials to create a new API token.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. YepCode sits in that group, and the shape of its toolset — get_processes, create_process, get_process among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use YepCode.
• Written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the yepcode mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.