ADT command-line reference (adt)

Note  Reference only These commands are internal interfaces used by the ADT agent plugin. They are not intended to be invoked directly by an end user or developer. Describe the result you want, and let your coding agent choose and run the appropriate command.

adt manages projects, connected files, Web Viewer apps, type generation, deployment, and the toolkit itself. It is delivered by the coding agent plugin and primarily used by coding agents, but developers can also invoke it from scripts. Read this page to understand what each command does to your project and your FileMaker file.

Conventions

The coding agent runs each command in the context of an ADT project and, when required, its connected FileMaker file. The agent selects the command options, interprets its output, and handles its exit status. Commands that create components, layouts, or deployed apps can change the connected FileMaker file; the remaining commands inspect or update the local ADT installation and project.

adt init

Creates a project: manifest, agent instructions, and git repository. Takes no FileMaker file and installs no JavaScript toolchain.

adt connect

Registers a FileMaker file with the project, stores its credentials, and records it in the manifest. Also re-points an existing connection.

adt app

Scaffolds a Web Viewer app, registers it in the manifest, and manages its relationship to a connected file.

adt components

Reports what ADT has installed in a connected file, installs or updates it, and removes it. See ADT components in a file for the object inventory.

adt layout

Creates layouts in a connected file, including the layouts a generated data client needs.

adt typegen

Generates a typed client per configured layout. Its configuration fields and generated output are documented in adt.config.json.

adt deploy

Builds the production bundle, writes it into the connected file as a single HTML artifact, and reports what it replaced.

adt update

Reconciles what is in a project and its apps with the toolkit version installed on the machine. Distinct from installing a new toolkit build.

adt doctor

Reports overall readiness and fixes what it can. Its verdict is scoped to what the current folder and open file actually need.

adt logs

Prints the logs written by the CLI and the MCP server — the first thing to collect for a support request.

adt install and adt uninstall

Install or remove the parts of ADT that live on the machine, separately from anything installed in a FileMaker file.

adt mcp

Starts the MCP server that coding agents connect to, and reports how a client is configured to reach it. Not to be confused with the MCP tool reference, which documents the tools themselves.

adt agents

Registers ADT with a supported coding agent and manages the skills and instructions it installs.

adt standards

Lists, installs, and resolves the naming and structural standards an agent follows in a connected file.