cloud-functions

Use this skill when developing, deploying, and managing CloudBase cloud functions. CloudBase supports two types of cloud functions: Use this skill for cloud function operations when you need to: Do NOT use for: Choose the right function type Understand runtime limitations Deploy functions correctly Query logs properly ⚠️ CRITICAL: Runtime cannot be modified after function creation Once a cloud function is created with a specific runtime, the runtime cannot be changed . If you need a different runtime: Supported Node.js Runtimes: Runtime Selection Guidelines: Event functions require: Function Directory : Contains function code Function Root Path : Parent directory containing function directories Entry Point : Default is index.js with exports.main Creating New Functions: Use createFunction tool (see MCP tool documentation for full parameter list): Updating Function Code: Use updateFunctionCode tool: Deployment Best Practices: HTTP Functions are optimized for Web service scenarios, supporting standard HTTP request/response patterns. Key Characteristics: ⚠️ CRITICAL: HTTP Functions require scf_bootstrap file Examples: Node.js Example (Express): MCP Tool: CLI: ⚠️ Notes: Method 1: HTTP API (with Access Token) ⚠️ Must include webfn=true parameter Method 2: HTTP Access Service (Custom Domain) Use createFunctionHTTPAccess MCP tool to configure HTTP access: SSE (Server-Sent Events):...