Understand your FileMaker solution. Edit scripts as text. Paste them back.
KiBuild MCP helps your AI assistant find scripts, trace field usage, and understand relationships from your FileMaker XML export. FM Bridge lets you edit script steps in your code editor, with or without AI, and paste them back into FileMaker. Two free tools: use either on its own, or bring them together in one workflow.
FileMaker solutions hold years of business logic, but AI tools struggle to find their way around them, and whatever an AI writes still has to be rebuilt by hand in Script Workspace. KiBuild MCP lets your AI find its way around your solution. FM Bridge turns scripts into text you can edit and paste back. KiBiz Systems built both for our own work and shares them free on KiHub. More tools will follow.
KiBuild MCP helps your AI assistant work with your FileMaker solution. FM Bridge lets you edit script steps as text and paste them back. Each works on its own, and together they cover the whole change.
Helps your AI assistant find scripts, trace where fields are used, and follow relationships, using the XML export of your FileMaker solution.
Lets you edit FileMaker script steps as plain text in your code editor, with or without AI, then paste them back into FileMaker.
A client asks: “Add a 1.5% late fee to invoices that are more than 30 days overdue.” Here is how that change goes with both tools. You can also use either tool on its own.
Ask your AI which scripts and layouts use the invoice due date. KiBuild looks it up in your export, so you know what the change will touch before you open Script Workspace.
Which scripts and layouts use Invoices::DueDate?
Copy the steps of the invoice script in FileMaker and paste them into your editor with FM Bridge. Write the new steps yourself, or ask the AI to draft them, and review the result.
# Late fee after 30 days
If [ Get ( CurrentDate ) - Invoices::DueDate > 30 ]
Set Field [ Invoices::LateFee ; Invoices::Total * 0.015 ]
End If
Press one shortcut to turn the text back into FileMaker steps, paste them into Script Workspace, and run the script on a test invoice.
Cmd+Option+B (Ctrl+Alt+B on Windows)
then paste in Script Workspace
Illustration · the solution, scripts, and fields shown are made-up examples
Set up KiBuild once, then ask about any FileMaker file you export. Add FM Bridge whenever you want to edit scripts as text.
Paste one line into Terminal (PowerShell on Windows). The installer checks the download, then a setup wizard asks which AI tools you use and connects KiBuild to each one.
$ curl -fsSL https://raw.githubusercontent.com/KiBiz-Systems/kibuild-mcp/main/install.sh | sh
> irm https://raw.githubusercontent.com/KiBiz-Systems/kibuild-mcp/main/install.ps1 | iex
kibuild-mcp --setup --updateIn FileMaker, choose Tools → Save a Copy as XML… and save it into a
files/Source folder inside your project folder.
Save a Copy as XML [ Window Name: "MySolution"; Destination: "files/Source/MySolution.xml" ]
Open the project folder in your AI tool and ask it to process the export. KiBuild splits it into one file per object and builds a searchable index.
Explode my FileMaker export
> /init-kibuild-project
Ask in plain English. To check KiBuild is connected, look for 32 KiBuild tools in your AI tool's MCP list.
Where is Invoices::Status used?
> /mcp kibuild · 32 tools
Install the add-on in your editor, then copy script steps in FileMaker and press Cmd+Option+V (Ctrl+Alt+V on Windows) to paste them as text. Press Cmd+Option+B (Ctrl+Alt+B) to copy them back for FileMaker.
$ curl -LO https://github.com/KiBiz-Systems/FMBridge/releases/latest/download/fm-bridge-mac.vsix $ code --install-extension fm-bridge-mac.vsix
> curl.exe -LO https://github.com/KiBiz-Systems/FMBridge/releases/latest/download/fm-bridge-windows.vsix > code --install-extension fm-bridge-windows.vsix
Prefer clicking? Download for
macOS or
Windows,
then in your editor open Extensions → ⋯ → Install from VSIX…. Either way, finish with
Developer: Reload Window. In Cursor, Windsurf, or Antigravity, replace code
with cursor, windsurf, or antigravity-ide.
KiBuild reads the XML export, not your live file. After you change the solution, save a new export and ask the AI to process it again so its answers stay current.
KiBuild and FM Bridge do their processing on your computer. The AI tool you connect sends what it reads to its own AI service, under that service's terms.
Commands that start with / are for Claude Code. In other AI tools, use the terminal
commands and plain-English requests shown here.
KiBiz Systems builds and maintains FileMaker solutions for clients, often files someone else wrote. We built KiBuild MCP and FM Bridge for that work. Using them together, our development time has dropped by almost 50%.
Three parts of FileMaker work that used to take us the longest, and what changed.
Instead of opening script after script to work out how a file fits together, we ask, and the answer points to the places to look.
KiBuild MCPBefore renaming or removing a field, we see every script, layout, and calculation in the export that uses it, so a change doesn't break something we didn't know about.
KiBuild MCPThe slowest part used to be building each step by hand in FileMaker's dialogs. Now the AI drafts the steps as text and FM Bridge pastes them in.
FM Bridge + your AI toolThis is one example. KiBuild's biggest savings come from questions about where things are used, the questions that take the longest to answer by searching the export.
The ~50% figure reflects KiBiz Systems' own experience on our client projects. It
is not a controlled study, and your results will depend on your files and the kind of work you do.
About this example: Claude, one run, on the same file with
the same search and file-reading tools. The KiBuild run also had
KiBuild's tools and its processed copy of the export. Input tokens are as reported by Claude,
summed across every turn.
For developers who want the details. Full documentation is in each project's README: KiBuild MCP ↗ · FM Bridge ↗
files/Source/.
Single-file and split-catalog exports both work.explode_xml_export splits it into one file per object
under files/Schema/<db>/: scripts (with plain-text copies), tables and fields,
layouts, relationships, table occurrences, value lists, custom functions, and more.generate_schema_map writes workspace_map.md, an
index of every table, layout, table occurrence, and script folder, so lookups don't need to
read the raw XML.Find scripts, layouts, and tables by name. Inspect relationships. Keyword search the workspace_map.md index. Generate or refresh the schema map. The foundational lookup layer.
Trace where a script is called, where a field is used, or what references a table occurrence. Covers scripts, layouts, calculations, relationships, value lists, and variables.
Explode exports, extract steps, resolve IDs, trace dependencies, match revisions. Validate FMXML snippets and WebViewer HTML. Write versioned artifacts to the outbox.
Load domain-specific expertise into AI context. Pro and simple scriptwriter modes, script analysis, FM XML serializer, and script debugging. Skills shape how the AI applies the other 31 tools.
KiHub is built in the open by KiBiz Systems. Share ideas, ask questions, report bugs, and follow what's next — all in GitHub Discussions. No sign-up required beyond a GitHub account.
The official community hub for KiHub, KiBuild MCP, and FM Bridge. Feature requests, Q&A, and release announcements, all in one place.
KiHub is KiBiz Systems' open developer platform for FileMaker and AI. KiBuild MCP and FM Bridge are live today, and more projects will follow. Pull requests welcome — open an issue first for significant changes.