YepCode

You learn how to run and connect to the YepCode MCP Server so that AI platforms can execute and manage YepCode processes as tools. This server enables secure, real-time interaction with your workflows, turning YepCode processes into AI-accessible capabilities with flexible remote or local deployment options.

How to use

Connect your MCP client to either the remote hosted MCP server or a locally hosted instance. For remote usage, you can use the SSE endpoint when your client does not support authentication headers, or the HTTP endpoint when your client supports authorization headers. For local usage, you can run the server via NPX or Docker and point your client to the local instance.

Remote usage lets your AI platform request data and trigger YepCode processes over standard HTTP-based MCP endpoints. If your client does not send authentication headers, use the SSE URL that includes your API token. If your client supports headers, use the HTTP URL with an Authorization header containing your API token.

Local usage comes in two flavors. Use NPX to run the MCP server directly from the package registry, or run a Docker container. In both cases you provide your API token so the server can access your YepCode workspace.

If you need to inspect and debug the MCP server interaction, start the MCP Inspector to view debugging tools in your browser. This helps you ensure the server and clients exchange the expected messages and tool definitions.

How to install

Prerequisites: ensure you have Node.js version 18 or higher installed if you plan to use NPX. If you plan to run via Docker, ensure Docker is installed and running on your system.

Step 1. Obtain API credentials from YepCode Cloud.

Step 2. Choose your deployment method and configure the MCP client accordingly.

Remote Approach using SSE or HTTP server

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "url": "https://cloud.yepcode.io/mcp/sk-c2E....RD/sse"
    }
  }
}

Remote approach with authentication headers

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "url": "https://cloud.yepcode.io/mcp/sse",
      "headers": {
        "Authorization": "Bearer <sk-c2E....RD>"
      }
    }
  }
}

Local Approach using NPX

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "command": "npx",
      "args": ["-y", "@yepcode/mcp-server"],
      "env": {
        "YEPCODE_API_TOKEN": "your_api_token_here"
      }
    }
  }
}

Local Approach using Docker

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-d",
        "-e",
        "YEPCODE_API_TOKEN=your_api_token_here",
        "yepcode/mcp-server"
      ]
    }
  }
}

Available tools

run_code

Executes code in YepCode's secure environment and returns the result, logs, and any error message.

yc_api

Provides API management tools for managing processes, schedules, variables, storage, executions, and modules.

yc_api_full

Extends yc_api with additional tools for managing process and module versions.

get_processes

List processes with optional filtering.

create_process

Create new processes with source code.

get_process

Get details of a specific process.

update_process

Update an existing process.

delete_process

Delete a process.

get_process_versions

Get versions for a process (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.

update_schedule

Update a scheduled process.

get_variables

List team variables.

create_variable

Create a new variable.

update_variable

Update an existing variable.

delete_variable

Delete a variable.

get_storage_objects

List storage objects.

upload_storage_object

Upload a file to storage.

download_storage_object

Download a file from storage.

delete_storage_object

Delete a file from storage.

get_executions

List executions with optional filtering.

get_execution

Get details of a specific execution.

kill_execution

Terminate a running execution.

rerun_execution

Rerun a previous execution.

get_execution_logs

Get logs for an execution.

get_modules

List script library modules.

create_module

Create a new module.

get_module

Get module details.

delete_module

Delete a module.

get_module_versions

Get versions of a module (requires yc_api_full).

get_module_version

Get a specific module version (requires yc_api_full).

delete_module_version

Delete a module version (requires yc_api_full).

get_module_aliases

Get module version aliases (requires yc_api_full).