Install ADT

Requires a Mac with FileMaker Pro 26.1 or later installed — see System Requirements.

Install the package

  1. Get the installer.

    ADT is distributed as a signed, notarized macOS installer package, adt-<version>-build.<n>-installer.pkg.

    Note  Request a build There's no public download location. Obtain the current build through the private group in Claris Community.

  2. Run the .pkg.

    The installer:

    • Adds filemaker, the FileMaker CLI used for schema, script, and layout work, to your PATH at /usr/local/bin/filemaker — the one directory on a stock macOS PATH the installer can write.

    • Installs the standard ADT agent plugin into Cursor, the Codex CLI, the ChatGPT desktop app, and VS Code. If it detects Claude Desktop or the Claude Code CLI, it also installs the Claude plugin. These integrations carry ADT's skills, register the MCP tools, and contain the adt binary that drives them. See Manual configuration if that step didn't run.

    • Stages the component bundle ADT applies to your files, the project template, and the filemaker agent skill under ~/Library/Application Support/ADT/MCP/.

    Note  adt is not a command you run The adt binary lives inside the agent plugin and is not on your PATH. Your agent calls it; you don't. See What ADT installs for which parts are yours to run.

  3. Restart affected apps.

    Restart any supported coding agents that were running during installation so they pick up the ADT plugin. If FileMaker Pro was open during installation, quit and reopen it too: the installer enables the FileMaker Pro feature that makes the Agents menu item visible, and it appears only after a restart.

  4. Turn on Agent Access in FileMaker Pro.

    ADT reaches FileMaker Pro through its built-in Agent Access, not a plugin. In FileMaker Pro 26.1 or later, open File → Manage → Agents, tick "Enable Agent Access for this application", and leave the port at 19080. If you use a different port, set FM_DEV_SERVER_PORT in your shell profile or coding agent host to match it. This is a one-time setting per copy of FileMaker Pro — it stays on until you turn it off. See System Requirements for the persistent setup. If Manage Agents is not in the menu, see The Manage Agents Option Is Missing.

    The first time ADT runs a script in a file, FileMaker Pro shows a prompt asking you to allow it. adt connect raises this prompt as its last step, so answer it when you see it. The grant lasts until you quit FileMaker Pro; after a restart, the first call to each file asks again. See Grant Agent Access to a file.

Verify the agent plugin (optional)

You can skip this check and continue to the next step. When your coding agent responds to an ADT prompt and starts the setup, that also confirms the plugin is installed.

If you want to check before continuing, open your coding agent and confirm FileMaker Agentic Development appears in its installed plugins:

Cursor

  1. Open Customize in the sidebar.

  2. Find FileMaker Agentic Development in your installed plugins.

  3. Confirm it is enabled.

Codex CLI

Run:

Copy 
codex plugin list --marketplace Claris

Confirm filemaker-agentic-development@Claris is listed as installed, enabled.

ChatGPT desktop

  1. Open Plugins.

  2. Find FileMaker Agentic Development in your installed plugins.

  3. Confirm it is marked Installed.

Use ADT from Codex mode. A regular ChatGPT conversation cannot work inside a project folder.

VS Code

  1. Open the Chat view and select the gear icon.

  2. Select Plugins.

  3. Confirm FileMaker Agentic Development appears and is enabled.

Claude Desktop

  1. Open Customize in the left sidebar.

  2. Select Plugins.

  3. Confirm FileMaker Agentic Development appears in your installed plugins.

Use ADT from the Code tab, which runs Claude Code inside a project folder. A regular chat cannot reach your FileMaker file.

Claude Code CLI

  1. Start Claude Code.

  2. Enter /plugin and open the Installed tab.

  3. Confirm FileMaker Agentic Development appears and is enabled.

If the plugin is missing, rerun the .pkg installer. Then quit and reopen that coding agent before checking again.

Next step

Open your FileMaker file in FileMaker Pro (hosted or local), then see Connect a FileMaker File to create a project and connect it.