Patchwork
Related Servers
Alternatives to Patchwork
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that connects Claude to FileMaker databases via the Data API, enabling natural language queries, record management, layout exploration, and script execution.11MIT
- AlicenseAqualityBmaintenanceMCP server that gives Claude Desktop and other desktop MCP clients filesystem powers—read, write, edit, and manage files like AI coding assistants.1777 npm9MIT
- AlicenseAqualityCmaintenanceAn MCP server that provides AI assistants with direct access to FileMaker databases via OData v4 API, enabling CRUD operations, script execution, and schema introspection.196MIT
- AlicenseAqualityDmaintenanceAn MCP server and HTTP gateway that dispatches coding tasks to Claude Code, Codex, and Antigravity CLI sessions, keeps track of those sessions, and optionally runs an implement → review → verify loop against a real repository.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables external MCP clients like Claude Desktop, Claude Code, Cursor and Zed to hand work to a local crew of AI agents that plan, write, check and fix code in a folder, while also acting as an MCP client that can use their tools. Runs locally with user-supplied keys, approval-gated commands, diffable and undoable runs.AGPL 3.0
- AlicenseAqualityDmaintenanceMCP server that combines Read+Edit file operations into single tool calls. 80-95% fewer tool calls formulti-file refactoring across Claude, Cursor, Windsurf, and more.330 npm3MIT
TDQS
Scored across 21 tools
Most tools target a distinct resource+action, and the descriptions actively disambiguate the tricky pairs (add_script vs set_steps vs append_steps, retheme vs recolor_layouts, replace vs push). The main residual overlap is patchwork_replace, which can touch layouts, themes, value lists and custom functions and thus shadows the specialised tools, though the descriptions explicitly steer callers elsewhere first.
All 21 tools share the patchwork_ prefix and snake_case, with verb_noun forms (add_field, place_field, set_steps, recolor_layouts) dominating. A handful of read-only tools use bare nouns (status, log, palette, uses), which is a minor but readable deviation.
21 tools sits at the heavy end of the scale, but the domain genuinely spans file lifecycle, object CRUD across five object kinds, script step editing, styling, versioning and export, so most tools earn their place. The surface could be tightened (replace and push are catch-alls) but nothing is obviously redundant.
The lifecycle is well covered: open, inspect, add/edit/delete objects, version with undo and log, and save out to a new .fmp12. Gaps remain for creating tables or layouts from scratch and for renaming objects (the uses tool hints at renaming but no rename tool exists), forcing callers into raw XML via replace or push.