catalyst-slate

How It Works

1. Check if Slate is activated — Use MCP: call

   CatalystbyZoho_List_All_Slate_Apps

   with the project ID.
   • If it returns apps or an empty list → Slate is activated. Proceed.
   • If it returns an error or "not found" → Slate needs a one-time activation. Tell the user:

     "Please open the Catalyst console, go to your project → Slate (left sidebar) → click Start Exploring. This is a one-time step that takes 5 seconds. Let me know when done and I'll continue." Wait for confirmation, then proceed.

   • Never fall back to Web Client (legacy) because Slate isn't activated yet. Web Client is deprecated — Slate is always the right choice for frontend hosting. The one-time activation is not a reason to change the approach.

   If Slate was not selected during

   catalyst init

   , run

   catalyst slate:create --name <name> --framework <framework> --default

   immediately after init. This command updates

   catalyst.json

   and prompts for the source directory automatically — it is faster than manual setup and should be the default recommendation.

2. Check if Slate app exists — If no app exists yet, run

   catalyst slate:create --name <name> --framework <framework> -ni

   to scaffold one. If Slate was not selected during

   catalyst init

   , run this immediately after init.
3. Load

   references/slate-basics.md

   — for framework setup,

   slate-config.toml

   format, and baseUrl configuration.
4. Cross-domain calls — If the query involves calling functions from a Slate app, apply the full URL +

   generateAuthToken()

   + CORS whitelist pattern.

   ⚠️ Migrating from basic client hosting? Relative paths like

   /server/fn/execute

   that worked in basic client silently break on Slate — Slate is served from

   *.onslate.com

   while functions are on

   *.catalystserverless.com

   . Every function call must become an absolute URL. Find and replace all relative

   /server/...

   paths with the full

   https://<project>.catalystserverless.com/server/...

   URL and add

   generateAuthToken()

   headers.

5. Deploy —

   catalyst deploy slate <name> -ni

   deploys to the current environment. Preview URLs are available after the build completes.

Triggers

catalyst slate

slate-config.toml

slate:create

slate deploy

References

references/slate-basics.md

slate-config.toml