Configuration

The MCP server can expose your YepCode processes as individual MCP tools. Each process becomes a callable tool that AI assistants can invoke.

Tag a process with mcp-tool and it is automatically exposed as an MCP tool. No configuration needed.

For custom tags, add them to YEPCODE_MCP_TOOLS so the MCP server discovers those processes:

1. Tag your process (e.g. core, automation)
2. Include that tag in YEPCODE_MCP_TOOLS (see below)
3. The process appears as a tool named after its slug (or yc_<processId> if the slug is longer than 60 characters)

• Each process tool accepts parameters according to the process input schema (JSON Schema). Define a proper schema for better AI behavior.
• Sync (default): waits for completion, returns executionId, logs, returnValue, error
• Async: pass synchronousExecution: false to get executionId immediately

Common issues: No process tools with custom tags? Add those tags to YEPCODE_MCP_TOOLS. Tool not found? Ensure tag spelling matches. See Process tags for how to add and manage tags.

• Built-in categories: run_code, yc_api, yc_api_full
• Individual tools: e.g. execute_process_sync, get_execution
• Custom process tags: e.g. core, automation — add tags to expose those processes (processes tagged mcp-tool are always exposed; see “Processes as tools” above)

YEPCODE_MCP_TOOLS — enable run_code, basic API, and processes tagged core:

"env": {
  "YEPCODE_API_TOKEN": "your_token",
  "YEPCODE_MCP_TOOLS": "run_code,yc_api,core"
}

YEPCODE_MCP_OPTIONS — keep run_code source for audit and skip coding rules in the tool schema:

"env": {
  "YEPCODE_API_TOKEN": "your_token",
  "YEPCODE_MCP_OPTIONS": "runCodeCleanup,skipCodingRules"
}

Both — combine tool selection and options:

"env": {
  "YEPCODE_API_TOKEN": "your_token",
  "YEPCODE_MCP_TOOLS": "run_code,yc_api,core",
  "YEPCODE_MCP_OPTIONS": "runCodeCleanup,skipCodingRules"
}