How It Works

Verify local scaffold — both catalyst init and functions:add support non-interactive mode (CLI v1.27.0+). Check whether .catalystrc and catalyst.json exist. If missing, use MCP tools to get the org ID and project ID, then run:
```
catalyst init --org <orgId> -p <projectId> -ni
```
Never ask the user to run catalyst init interactively. NI mode can only link an existing project — if none exists, tell the user to create one in the console first. Once initialized, add functions non-interactively:
```
catalyst functions:add --name <name> --type <type> --stack <stack> -ni
# e.g. catalyst functions:add --name api --type aio --stack node20 -ni
```
Identify the function type — Basic I/O for simple request/response, Advanced I/O for raw HTTP control, Event for trigger-based, Cron/Job for scheduled, Integration for Zoho service events, Browser Logic for Puppeteer.
Load references/functions-basics.md — for the matching handler signature, catalyst-config.json keys, SDK init pattern, and CORS setup.
Load references/functions-advanced.md — for file uploads (busboy), streaming responses, error handling, or chaining functions.
Load references/api-gateway.md — for routing rules, rate limiting, or gateway-level CORS.
Validate config — Confirm catalyst-config.json uses deployment + execution keys only. Never use function or entry_point.

catalyst-functions