Manual configuration
Note Manual configuration is usually not necessary The ADT installer automatically configures supported coding agents. Use this page for another coding agent that can load an Agent Plugin package, or when automatic configuration did not complete.
ADT supplies FileMaker Agentic Development as a portable plugin. The package includes the adt toolset, the adt-mcp server, and ADT's skills. A coding agent must support the Agent Plugin standard or the Claude plugin format to load the complete package.
The exact command or screen used to add a local plugin depends on the coding agent. Follow that agent's instructions for adding a local plugin or local plugin marketplace, using the paths below.
Before you begin
Run the ADT .pkg installer first. Manual configuration only connects a coding agent to files the installer has already placed on your computer. It does not install the filemaker binary, the ADT FileMaker plug-in, or the file-component bundle.
See Install ADT if the toolkit is not installed yet.
Choose the package format
The installer stages two formats under ~/Library/Application Support/ADT/MCP/:
| If the coding agent supports | Give it this local path |
|---|---|
| Agent Plugin standard | ~/Library/Application Support/ADT/MCP/agent-plugin/
|
| Agent Plugin marketplace | ~/Library/Application Support/ADT/MCP/.agents/plugins/marketplace.json
|
| Claude plugin marketplace | ~/Library/Application Support/ADT/MCP/claude-plugin/
|
Use the Agent Plugin format when the client supports it. Use the Claude marketplace only for a client that explicitly supports the Claude plugin format.
The plugin identifier is filemaker-agentic-development. A marketplace-based client may display it as FileMaker Agentic Development from the Claris marketplace.
Configure the coding agent
-
Open the coding agent's plugin or customization documentation.
-
Follow its procedure for adding a local plugin directory or local marketplace.
-
Supply the matching path from the table above.
-
Select FileMaker Agentic Development if the client asks you to choose a plugin from the marketplace.
-
Confirm the plugin is installed and enabled, then restart the coding agent.
Do not copy the MCP server and skills into separate configuration files. Loading the plugin keeps those pieces together and lets the agent resolve paths inside the installed package.
See The ADT agent plugin for a complete inventory of what the package contains.
Verify the plugin
After restarting the coding agent, ask it to check the plugin before you continue:
Confirm that the FileMaker Agentic Development plugin is installed and loaded.If the plugin is missing, confirm the client supports one of the package formats above and that you supplied the correct path. Then rerun the ADT installer, repeat the client's plugin procedure, and restart the coding agent before checking again.