vxil

The Vxil CLI — config-as-code for backend building blocks you enable in one line.

npx @vxil/cli quickstart          # create a tenant + scaffold vxil.config.ts
npx @vxil/cli push                # apply your config (features, cms collections, functions)
npx @vxil/cli gen                 # generate a typed client + MCP manifest for YOUR backend
npx @vxil/cli functions dev fn    # run a tenant function locally against the remote edge
npx @vxil/cli listen --forward-to localhost:3000/webhook   # forward inbound webhook events to your local server
npx @vxil/cli mcp install --client cursor   # wire your backend's MCP server into your editor's agent
npx @vxil/cli doctor              # sanity-check keys, URLs, reachability

Config-as-code lives in vxil.config.ts, typed via the bundled vxil/config subpath:

import { defineConfig } from '@vxil/config';

export default defineConfig({
  features: {
    auth: { enabled: true, methods: ['email_otp'] },
    cms: { enabled: true, collections: { tasks: { fields: { title: 'text', done: 'boolean' } } } },
    notifications: { enabled: true, provider: 'resend' },
  },
});

Verbs: init quickstart push pull diff gen secrets env seed export import functions listen mcp cms dev doctor versions rollback link apply migrate try.

vxil listen --forward-to <url> polls your tenant's inbound webhook events and re-POSTs each new one to your local server under the exact delivery contract production uses — same body shape, same signed X-Vxil-Jobs-Signature header (your real signing secret) — so the handler you test locally is the handler you ship. --replay-last <n> re-forwards recent events; --raw posts the stored provider payload alone.

Docs: vxil.com · Dashboard: vxil.com/dashboard

MIT © techmaker.io