MY-MCP vs OttoFMS MCP — A Head-to-Head Comparison With OttoFMS recently launching their MCP server feature, I thought it was worth comparing it against MY-MCP. Both connect AI clients like Claude to FileMaker data — but they take fundamentally different approaches. The Key Philosophical Difference OttoFMS MCP is a script gateway. The intelligence lives in your FileMaker scripts. It exposes your existing scripts as MCP tools, configured through the Otto Console GUI — no code required on the MCP side. MY-MCP is a query engine. The intelligence lives in the server itself. Schema discovery, OData query building, field quoting, date normalization, multi-tenant switching, and LLM-optimized output all happen automatically — no FM scripting required to get started. ( 1 script that returns DDL) Where OttoFMS Wins Write operations out of the box (create, update, delete via FM scripts) No code needed — GUI configuration Server-side hosting — no local install per user Where MY-MCP Wins Zero-config querying — connect and immediately query any table Automatic schema discovery at runtime Multi-tenant — one server, multiple FM databases In-memory analytics without additional FM round trips Bottom Line: They're Complementary Use MY-MCP for reads, discovery, and analytics. Use OttoFMS for write operations via existing FM scripts. They solve different problems and pair well together.