Replaced disableRunCodeTool with new flexible tools argument in MCP server

In our MCP server, we’ve replaced the disableRunCodeTool flag with a new, more flexible tools argument. This change gives users fine-grained control over which tools are enabled.

You can now define which tools are enabled by using a comma-separated list of built-in tool categories and process tags:

• Built-in categories: run_code: Enables the code execution tool executions: Enables execution management tools env_vars: Enables environment variable management tools storage: Enables storage management tools

• Process tags: Any tag used in your YepCode processes (e.g. mcp-tool, core, api, automation, etc.). When specified, all processes with that tag are exposed as individual MCP tools.

If no tools are specified, all built-in tools are enabled by default, but no process tools are exposed.

Example SSE URL definition:

https://cloud.yepcode.io/mcp/sk-c2E....RD/sse?mcpOptions=runCodeCleanup&tools=run_code,storage,env_vars,core,api