Hosting

remote and local/self-hosted

Transport

Hosted endpoint uses Streamable HTTP; local server uses stdio.

Endpoint

https://cloud.yepcode.io/mcp

Authentication

Hosted: API Credential token either embedded in endpoint path or supplied as Bearer header; hosted OAuth 2.0 Client Credentials is documented. Self-hosted: YEPCODE_API_TOKEN from YepCode Settings ? API Credentials.

Requirements

• YepCode account and API Credential with MCP endpoint access for hosted setup.
• Self-hosting requires Node.js 18+ and a YepCode API token; Docker is an alternative documented path.
• Tools depend on enabled built-in categories and the user's configured/tagged processes.

Setup steps

1. For hosted setup, create an API Credential with MCP endpoint access in YepCode Settings ? API Credentials.
2. Add https://cloud.yepcode.io/mcp to a remote-capable MCP client and provide the credential using the client's supported secret/header mechanism; the vendor also documents a token-in-path URL form.
3. Alternatively, for self-hosted local use, configure command npx with args -y @yepcode/mcp-server and set YEPCODE_API_TOKEN in the client's local environment configuration. Requires Node.js 18+.
4. For Docker self-hosting, build the repository image and launch it with -i --rm and YEPCODE_API_TOKEN as an environment variable, as in the official quickstart.
5. Optional: select tools through YEPCODE_MCP_TOOLS; process tools require the default mcp-tool tag or a custom tag listed in that variable.
6. After adding the endpoint, complete the client's auth/token flow and verify that the expected tool list appears. Run code only when intentionally requested; no connection test was performed for this record.

The 43 stored names are a documented built-in reference inventory, not a fixed live count: built-in tool categories are configurable, and tagged user processes become additional dynamic tools. Confirm tools/list on the connected account for its exact inventory.

• run_code

  Execute JavaScript or Python in YepCode's isolated environment; optional language, comment and runtime settings.

  01
• set_env_var

  Set a YepCode workspace environment variable; sensitivity masking defaults to enabled.

  02
• remove_env_var

  Remove an environment variable from the YepCode workspace.

  03
• list_files

  List YepCode Storage files, optionally filtered by path prefix.

  04
• upload_file

  Upload text or base64-encoded binary content to YepCode Storage.

  05
• download_file

  Download a YepCode Storage file; binary content may be returned as base64.

  06
• delete_file

  Delete a YepCode Storage file.

  07
• get_processes

  List processes with optional filtering.

  08
• create_process

  Create a process from source code.

  09
• get_process

  Get process details.

  10
• update_process

  Update an existing process.

  11
• delete_process

  Delete a process.

  12
• get_process_versions

  List process versions; requires yc_api_full.

  13
• execute_process_async

  Execute a process asynchronously.

  14
• execute_process_sync

  Execute a process synchronously.

  15
• schedule_process

  Schedule a process.

  16
• get_schedules

  List scheduled processes.

  17
• get_schedule

  Get schedule details.

  18
• pause_schedule

  Pause a scheduled process.

  19
• resume_schedule

  Resume a paused schedule.

  20
• delete_schedule

  Delete a schedule.

  21
• update_schedule

  Update a scheduled process.

  22
• get_variables

  List team variables.

  23
• create_variable

  Create a team variable.

  24
• update_variable

  Update a team variable.

  25
• delete_variable

  Delete a team variable.

  26
• get_storage_objects

  List storage objects through the API.

  27
• upload_storage_object

  Upload an object through the API.

  28
• download_storage_object

  Download an object through the API.

  29
• delete_storage_object

  Delete a storage object through the API.

  30
• get_executions

  List executions with optional filtering.

  31
• get_execution

  Get execution details.

  32
• kill_execution

  Stop a running execution.

  33
• rerun_execution

  Rerun a previous execution.

  34
• get_execution_logs

  Get execution logs.

  35
• get_modules

  List script library modules.

  36
• create_module

  Create a script library module.

  37
• get_module

  Get module details.

  38
• delete_module

  Delete a module.

  39
• get_module_versions

  List module versions; requires yc_api_full.

  40
• get_module_version

  Get a specific module version; requires yc_api_full.

  41
• delete_module_version

  Delete a module version; requires yc_api_full.

  42
• get_module_aliases

  Get module version aliases.

  43

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Tool availability varies with YEPCODE_MCP_TOOLS, account permissions, and process tags; user-defined process tools are dynamic.
• The hosted endpoint requires an API Credential with MCP endpoint access; availability/plan eligibility depends on the account.
• Several tools can execute code, change workspace settings, create/update/delete resources, or trigger processes; treat as potentially consequential.
• No live connection test performed.

• Repository README emphasizes locally supplied YEPCODE_API_TOKEN; the newer official hosted quickstart additionally documents hosted endpoint OAuth 2.0 Client Credentials and API Credential URL/header forms. These are separate deployment modes, not a conflict.
• README and current docs describe account-dependent dynamic process tools; a fixed total tool count is not supportable.

• primary source

  Official product identity and overview; links quickstart/configuration/tool-reference docs.

• primary source

  Hosted endpoint, API credential prerequisite, token and OAuth options, local NPX/Docker recipes, Node requirement and verification notes.

• primary source

  Dynamic process exposure, tags, environment variables, options, tool selection and common setup errors.

• primary source

  Official repository README, npm install configuration, Docker setup, documented tool names, MIT license and linked vendor site.

• primary source

  Repository package metadata checked for npm package and version 1.6.0.

• official tool reference

  Official current reference for built-in MCP tools; available built-ins depend on enabled categories and user-tagged processes are dynamically exposed.

Documentation checked 2026-10-28. Connection has not been runtime tested.