Saltar al contenido principal

Configure your app with AI

Appilot apps are configured by describing a content model: the views, controls, forms, action plans, and knowledge the agent reads to act inside your app. Authoring that by hand is easy to get subtly wrong: a flow that opens a field but never submits, a selector that breaks on the next render, half-translated labels, a knowledge article that is really a procedure.

The app-configurator turns that into a conversation. You install one skill (and its companion MCP server) into your AI tool of choice, then ask it to set up, audit, fix, and validate your app's configuration, checked against a formal config health contract.

What it does

  • Reads your app's content model and explains it in plain language.
  • Validates it against the health contract and returns a prioritized, severity-ranked report (critical → low), each finding with the exact fix.
  • Fixes issues with your consent. The server re-validates every write.
  • Soaks the live page to confirm selectors and plans actually resolve against the rendered DOM.

Works with your tools

The skill follows the open Agent Skills standard, so it installs into Claude Code, Codex CLI, Cursor, and other standard-compatible agents. The same file, no per-tool variants. Claude Desktop installs it as a single double-clickable bundle.

ChatGPT and claude.ai work differently: neither can start a program on your machine, so both connect over HTTPS to an Appilot MCP endpoint your team deploys. You supply your service token once, on a consent screen.

Without the MCP server the skill still works in advisory mode: paste or export your config and it audits it by reasoning against the contract.

Cloud or on-premise

The MCP server is endpoint-agnostic. Point it at a cloud tenant or your own on-premise / sovereign instance with one setting; the skill never hard-codes a host. The static validation runs locally with no network, so it works air-gapped. A fully sovereign setup (your instance, your model, this tooling) can run with no outbound traffic.

Next steps