Lets an AI agent edit FileMaker structures including fields, scripts, value lists, layouts, and themes with reversible changes.
Also known as Abdeltoto/patchwork-filemaker-mcp, patchwork-filemaker-mcp, filemaker-patchwork
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.0
- Last commit
- Nov 13, 2026
- License
- MIT
What is Patchwork MCP?
Patchwork lets an AI agent edit FileMaker structures including fields, scripts, value lists, layouts, and themes with reversible changes.
Summary generated from the project's README
About Patchwork MCP server
Developers working with Claris FileMaker can use Patchwork to allow AI agents to modify database structures through natural language. Instead of manually clicking through dialogs to define fields or adjust layouts, you can instruct an agent to perform these structural changes directly on a working copy of your .fmp12 file. This server is designed for local development, requiring the Claris command-line tools like FMUpgradeTool and FMDeveloperTool to be installed on your machine.
Patchwork functions as a safety layer between your AI client and the binary FileMaker format. It manages the complexity of UUIDs and XML exports, ensuring that every change is verified by re-exporting the file to prevent silent failures. It supports a wide range of structural tasks including adding or deleting fields, writing scripts, managing value lists, and restyling layouts or themes. The system maintains a versioned history of all modifications, allowing you to undo changes easily while keeping your original source file untouched.
What you can do with it
- 1Script generation and editingHave an AI agent write new scripts or modify existing ones using plain-text steps.
- 2Visual rebranding of solutionsInstruct an agent to change the colors and fonts across your entire FileMaker theme.
- 3Safe structural cleanupUse the agent to delete unused layouts while receiving warnings about dependent scripts.
Written from the project's README. Every use case is checked against a quote from it.
How to install Patchwork MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Patchwork MCP in Claude Code
$ claude mcp add --env 'PATCHWORK_PASSWORD=<YOUR_PATCHWORK_PASSWORD>' patchwork-filemaker-mcp -- uvx filemaker-patchworkInstall Patchwork MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"patchwork-filemaker-mcp": {
"command": "uvx",
"args": [
"filemaker-patchwork"
],
"env": {
"PATCHWORK_PASSWORD": "<YOUR_PATCHWORK_PASSWORD>"
}
}
}
}Install Patchwork MCP in VS Code
.vscode/mcp.json
{
"servers": {
"patchwork-filemaker-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"filemaker-patchwork"
],
"env": {
"PATCHWORK_PASSWORD": "<YOUR_PATCHWORK_PASSWORD>"
}
}
}
}Install Patchwork MCP in VS Code CLI
$ code --add-mcp '{"name":"patchwork-filemaker-mcp","type":"stdio","command":"uvx","args":["filemaker-patchwork"],"env":{"PATCHWORK_PASSWORD":"<YOUR_PATCHWORK_PASSWORD>"}}'Install Patchwork MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"patchwork-filemaker-mcp": {
"command": "uvx",
"args": [
"filemaker-patchwork"
],
"env": {
"PATCHWORK_PASSWORD": "<YOUR_PATCHWORK_PASSWORD>"
}
}
}
}Install Patchwork MCP in Codex
$ codex mcp add patchwork-filemaker-mcp --env 'PATCHWORK_PASSWORD=<YOUR_PATCHWORK_PASSWORD>' -- uvx filemaker-patchworkInstall Patchwork MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.patchwork-filemaker-mcp] command = "uvx" args = ["filemaker-patchwork"] [mcp_servers.patchwork-filemaker-mcp.env] PATCHWORK_PASSWORD = "<YOUR_PATCHWORK_PASSWORD>"
Install Patchwork MCP in Gemini CLI
$ gemini mcp add -s user -e 'PATCHWORK_PASSWORD=<YOUR_PATCHWORK_PASSWORD>' patchwork-filemaker-mcp uvx -- filemaker-patchworkInstall Patchwork MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"patchwork-filemaker-mcp": {
"command": "uvx",
"args": [
"filemaker-patchwork"
],
"env": {
"PATCHWORK_PASSWORD": "<YOUR_PATCHWORK_PASSWORD>"
}
}
}
}Configuration
PATCHWORK_PASSWORDSecretPassword of the FileMaker account used to open the file. Leave empty for files with no password.
| Name | Description | |
|---|---|---|
| PATCHWORK_PASSWORD | Password of the FileMaker account used to open the file. Leave empty for files with no password. | Secret |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableabdeltoto/patchwork-filemaker-mcp is public and reachablegithub.com/abdeltoto/patchwork-filemaker-mcp ↗Pass
- Package names this repository as its sourcefilemaker-patchwork names abdeltoto/patchwork-filemaker-mcp as sourcepypi.org/project/filemaker-patchwork/ ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for filemaker-patchworkpypi.org/project/filemaker-patchwork/ ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/abdeltoto/patchwork-filemaker-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from filemaker-patchworkPass
- No critical advisory in the package or its dependencies1 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub
Quick start · Examples · Connect your agent · What it can change · Field guide · Français
Friday, 4 PM. A client asks for "just one more field" on the detail layout. You know the drill: define the field, copy the label, nudge every object below it, stretch the part… then do it all again on the next layout.
Patchwork lets your AI agent do those clicks for you. Just ask, in your own words, the way you would ask a colleague. Your agent adds the field and places it right where you said, writes scripts, creates value lists and restyles layouts, in a real
.fmp12file. Every change is checked, every change can be undone, and your original file is never touched.
Free and open source. Works with Claude Code, Cursor, Codex and Antigravity.
Quick start
Three commands, then you just talk to your agent.
pip install filemaker-patchwork
patchwork doctor # finds the Claris command-line tools
patchwork init . # wires this folder for Claude Code, Cursor, Codex and Antigravity
No install with uv: uvx filemaker-patchwork doctor, and uvx filemaker-patchwork mcp as the MCP server command.
Then ask your agent: "Open Invoice.fmp12 and add a Status field to Clients." That's it.
Good to know
- It changes structure, not records. Fields, scripts, layouts, value lists, themes. For your data, use the Data API or OData.
- It works on closed files, not hosted ones. Edit a copy, test it, then deploy it as you usually do.
- It needs the Claris command-line tools (FMUpgradeTool and FMDeveloperTool). They come with the FileMaker Server installer, the free trial works, and no server has to run: install the Claris tools. Patchwork itself has no other dependency.
See it in action
Four real sessions on the free Claris Invoice solution. For each one: what was asked, what the agent did, and the file before and after. No mockups.
How it works
Why can't your agent just do this on its own? A FileMaker file is a binary file, and its structure hides behind dialogs an agent cannot click. Claris does ship a command-line way in, FMUpgradeTool, but it is picky: every object is addressed by a UUID, and a patch that is slightly wrong is silently skipped, while the tool still prints Patch File Applied.
Patchwork is the careful assistant in between:
| 🧵 Writes the patch | Reads the file's XML export and builds a patch with the right UUIDs, ids and catalog structure, so your agent doesn't have to |
| 🔍 Checks the result | Re-exports the file after every change and compares it with the previous version. If FileMaker skipped something, the change is refused, not silently lost |
| 🧭 Warns before breaking | Before a delete, it lists the scripts, layouts and calculations that use the object, and waits for your OK |
| 🕐 Keeps every version | Each change is a numbered version with its diff. Changed your mind? undo always works |
| 🔒 Protects the original | Everything happens on a working copy. save writes a new file and never overwrites yours |
More in how it works.
Connect your agent
One command sets everything up. Run patchwork init . in your project folder, new or existing: it adds the rules, the skills and the MCP configuration for every agent, and keeps the files you already have.
| Agent | Configuration written by init |
Then |
|---|---|---|
| Claude Code | .mcp.json · CLAUDE.md · .claude/skills/ |
Run claude in the folder and approve patchwork |
| Cursor | .cursor/mcp.json · .cursor/skills/ |
Enable patchwork in Settings › MCP |
| ⌨️ Codex | .codex/config.toml · AGENTS.md · .agents/skills/ |
Trust the project when Codex asks |
| Antigravity | .agents/mcp_config.json · AGENTS.md · .agents/skills/ |
Open the folder as a workspace |
Every agent gets the same 21 tools through patchwork mcp, a stdio MCP server. Your file's password stays yours: set it once in your shell with PATCHWORK_PASSWORD, and agents never see it. Manual setup and the full tool list: AI agents.
What it can change
Fields, plain-text scripts, value lists, colors and fonts, even a full rebrand. Every operation below was tried on real files and confirmed by re-exporting them.
| Add | Edit | Delete | |
|---|---|---|---|
| Fields · text, number, date, time, timestamp, container, calculation, global | ✅ | ✅ | |
| Scripts, read and written as FileMaker text | ✅ | ✅ | ✅ |
| Value lists | ✅ | ✅ | ✅ |
| Custom functions | ✅ | ✅ | ✅ |
| Layouts · place a field with its label, whole layout, colors, fonts, swap a field | ✅ field | ✅ | ✅ |
| Themes · colors, fonts, name | ✅ | ||
| Tables, table occurrences | 👁 read |
[!TIP] Scripts read and write the way the Script Workspace shows them, one step per line:
Set Field [ Clients::Status ; "Gold" ]. Edit the text ofpatchwork show script NAMEand send it back withset-steps: untouched lines keep their exact step, and every step is re-read after the change, so a dropped parameter is caught.
What FMUpgradeTool cannot do (record data, a brand-new theme, a single layout object on its own) is listed in the field guide.
Use it without an agent
Prefer the terminal? Everything the agent does is a plain command you can run yourself:
patchwork open "Invoice.fmp12" --account Admin # working copy, version v000
patchwork add-field Clients "Loyalty Tier"
patchwork add-value-list "Loyalty Tiers" Bronze Silver Gold
patchwork log # every version and what changed
patchwork undo
patchwork save "Invoice v2.fmp12"
| Command | What it does |
|---|---|
open SRC --account NAME |
Starts a working copy in .patchwork/ (version v000). The source is never modified |
status, log |
Current version, and every version with what changed |
ls [KIND] [TABLE] |
Lists layouts, scripts, value lists, custom functions, themes, tables, fields |
show KIND NAME |
Prints a script as FileMaker text (--xml for XML), anything else as XML. show step NAME prints a real example of a step |
add-field TABLE NAME |
Adds a field: --type, --calc, --global, --image logo.png |
add-value-list NAME VALUES... |
Adds a custom value list |
add-custom-function NAME --calc |
Adds a custom function, with --param |
add-script NAME STEPS.txt |
Creates a script from FileMaker script text (or <Step> XML) |
set-steps, append-steps |
Rewrites a script with edited text from show, or adds steps at the end |
place-field LAYOUT TO::FIELD --near FIELD |
Puts a field on a layout below another one, with a copy of its look and label. --side right, --label |
replace KIND NAME FILE.xml |
Replaces an object with your edited version of show |
uses KIND NAME |
Lists what references an object, and where its name appears in calculations |
delete KIND NAME |
Deletes a script, layout, value list, custom function or field. Refused while other objects reference it, unless --force |
retheme, recolor-layouts |
Rewrites colors and fonts of a theme, or of the layouts' local styles |
push PATCH.xml |
Applies a hand-written FMUpgradeTool patch, with the same checks |
undo |
Drops the last version |
save DEST |
Writes the current version to a new .fmp12 |
rebrand SRC DEST --brand brand.json |
One shot: colors, fonts, logo and theme name on a whole solution |
mcp |
The MCP server for agents |
init DIR |
Wires a folder for Claude Code, Cursor, Codex and Antigravity |
doctor |
Shows which Claris tools Patchwork found |
Every editing command takes -m "note" for the log and --dry-run to write the patch without applying it. More in examples and recipes.
The FMUpgradeTool field guide
The field guide collects every trap FMUpgradeTool sets without telling you, found the hard way on real files. Useful even if you never use Patchwork. A taste:
- without
--generateGUIDs, theme and field patches are skipped; - a layout's UUID is not the first
<UUID>inside it; - replacing one layout object is skipped, replacing the whole layout works;
- deleting a script step needs a
ScriptReferenceinside eachScriptStepReference.
Found another one? Add it.
FAQ
Contributing
Found a new FMUpgradeTool trap, wrote a recipe, or want a new operation? Everything is welcome: start with CONTRIBUTING.md. And if Patchwork gives you your Friday afternoon back, a ⭐ helps other FileMaker developers find it.
License
MIT. Patchwork is a community project, not affiliated with or endorsed by Claris International Inc. FileMaker and Claris are trademarks of Claris International Inc. Other product names and logos belong to their owners.
Patchwork MCP questions
How do I add Patchwork MCP to Claude Code?
Run claude mcp add --env 'PATCHWORK_PASSWORD=<YOUR_PATCHWORK_PASSWORD>' patchwork-filemaker-mcp -- uvx filemaker-patchwork in your terminal. Add --scope user to make it available in every project.
How do I add Patchwork MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does Patchwork change my data records?
No, it only changes the structure of the file such as fields, scripts, layouts, value lists, and themes. For data manipulation, you should use the Data API or OData.
Can I undo changes made by the AI?
Yes, every change is versioned and can be reverted using the undo command.
Does it work on hosted FileMaker files?
No, it works on closed files. You should edit a copy, test it, and then deploy it as usual.
What dependencies are required to run Patchwork?
It requires the Claris command-line tools (FMUpgradeTool and FMDeveloperTool) which are included with the FileMaker Server installer.