Agnes has published FM Dojo, which provides a comprehensive guide and tools for integrating AI into FileMaker workflows, focusing on practical implementation and best practices. New features and functions are regularly added.

Join Ernest and Todd in this episode of the Context Podcast, for a short demo of ProofKit MCP and how you can expose AI agents to FileMaker to build and publish Web Apps.

Alberto has released a Mac app - Windows to come - generate, copy-and-paste elements - scripts, custom functions, etc for coding via your favourite AI Agent, with usage based on 'credits' purchased.

Dimitris has released AI2FM - a plugin and service that connects AI models with FileMaker via copy-and-paste. The plugin supports natural language prompts to generate scripts and automate tasks. Bridge the Gap Between FileMaker and AI, Low-latency Vibe Coding for FileMaker. Turn any VS Code-compatible editor into a full FileMaker IDE — free — with autocomplete, live validation, hover docs, and autoformat for .fmscript. Then unlock the licensed XSLT round trip to copy script steps from FileMaker as readable text, edit with any AI agent (Claude, Codex, Gemini, Copilot, local LLMs), and paste straight back.

https://www.youtube.com/watch?v=7ArQ_T--BEY&t=2429s

Protect Your FileMaker Investment with ai2fm

https://ai2fm.com/protect-filemaker-investment.html

17 FileMaker Clipboard Bugs — verified, with reproducible test files
Published by ai2fm · companion to the v2.5 release · last updated 2026-07-28

During the R&D for ai2fm v2.5 we found, documented and reported to Claris International Inc. a set of 17 bugs in FileMaker’s clipboard serialisation. This page is the account of each one — but unlike a changelog, every claim here is backed by files you can download and reproduce yourself.

For each bug we ship a folder containing the FileMaker file itself plus real captures:
<Step>_<year>.fmp12 — the actual FileMaker file, one per version, so you can open the exact step we tested and copy it yourself.
<Step>_Source_<year>.xml — the exact clipboard FileMaker produced when we copied that step.
<Step>_Result_<year>.fmscript — what ai2fm made of that clipboard.

where a recovery exists, the corrected files that prove the fix round-trips.

Open the file, copy the same step in your own FileMaker, and you will get the same clipboard.

Download the test suite ⬇️ Bugs_Test_Suite.zip — 5.4 MB, every file referenced on this page

Bruno has created his own plugin to generate scripts, debug logic, ask questions, run structured queries against your file, and work with schema using context grounded in your live solution.

Matt is building a platform and plugin to analyse solutions, generate/update scripts, design layouts, build schema & more — all through AI that understands your live FileMaker environment. (em dashes optional)

A FileMaker-aware MCP server that gives AI coding tools deep, structured access to your FileMaker schema — scripts, layouts, tables, relationships, and dependencies — without grep, without reading raw XML, and without a FileMaker license at runtime.

Works with Claude Code, Cursor, Windsurf, Codex, Antigravity (Google), and any MCP-compatible AI tool.

Claris is preparing what comes next for FileMaker with agentic development and interface design.

Andrew Kear from Clockwork Creative Technology, with deterministic specs for Script, Layout, Table, Field & Value List XML.

Analyse a FileMaker solution in your browser

Nothing installed, nothing uploaded, works offline.

Clockwork Inspector (SaXML) Drop in a Save as XML export. Unreferenced fields tiered by confidence, broken references, script call tree, relationship graph drawn from the real TO geometry, layout wireframes, and a diff between two versions down to the calculation line. Every check is documented, so the findings are defensible in front of a client.

XML Scrubber (SaXML + others) Strips API keys, passwords and internal hostnames out of FileMaker XML before you hand it to an AI tool.

Reliable AI for FileMaker

AI is genuinely useful for FileMaker development, but only if it stops guessing. Left to its training data, a model invents functions that don't exist, and emits layout and schema XML that FileMaker rejects silently — no error, the object just never appears.

These are open tools and specifications that fix that: the knowledge an AI needs to generate FileMaker that actually works, and the tools to check what it produces. Much of it is reverse-engineering FileMaker's undocumented clipboard XML — the formats Claris has never published, where a wrong guess pastes silently and breaks. The rest is giving the model the vocabulary, reasoning and verification it otherwise lacks.

FileMaker Second Opinion A reasoning skill, not a knowledge file. It makes the model challenge its own first answer on exactly the problems where the common FileMaker solution works in a demo and fails silently in production, and it forces a proper read of Claris Help, Notes and platform sections included, before any behaviour claim is made. Built and refined against production work. New, and the piece the rest of this page stacks under.

FileMaker AI Vocabulary Every FileMaker 26 function and script step in ~7,000 tokens, so an AI stops inventing things that don't exist. The cheapest way to make any model better at FileMaker — no XML required.

Generation — paste-ready FileMaker XML

Script XML Skill (XMSS, XMSC, XMFN) The full script step ID dictionary, plus the hidden paste-handler rules that decide whether your XML survives the trip into FileMaker.

Layout XML Skill (XML2) All 18 layout object types mapped, every flag decoded, element order confirmed against native output. Verified across 45+ layouts in 10 production files.

Field, Table & Value List Definitions (XMFD, XMTB, XMVL) Field, table and value list definition XML — auto-enter, validation, storage, calculation options, and the three value list source arms — verified down to the individual option level.

Claris FileMaker Pro Skill is a skill in the pure sense, and a good one. It ships reference catalogs — all 360 calculation functions, all 155 script steps, the error codes, the help-center URLs — with a local-first, live-verify strategy and even a version-drift detector that flags when a fetched doc references a newer FileMaker version than the skill was built against. What it fixes is what the model knows: it stops your model from hallucinating a function signature or inventing an error code. That is real value. But it is, by design, a knowledge layer. The model still authors the XML; the skill just makes sure the model is better informed while it does that.