Can AI agents automate Claris FileMaker?

Claris FileMaker hosted databases are automatable today through the FileMaker Data API, the FileMaker OData API, and the FileMaker Admin API. The Data API is a REST interface for databases hosted on FileMaker Server or FileMaker Cloud. Server logins use HTTP Basic file-account credentials on /fmi/data/vLatest/databases/.../sessions; Cloud logins use a Claris ID FMID token. Later Data API calls send the returned Bearer session token. Opened pages document create, edit, delete, find, metadata, container upload, and script execution on layout-scoped /fmi/data/v1 and /fmi/data/vLatest paths. OData 4.0 is a second REST surface at /fmi/odata/v4/ with Basic auth on Server and FMID on Cloud. The Admin API is a separate REST surface for host administration; Server auth is Basic or PKI, Cloud auth is FMID, and access tokens expire 15 minutes after the last call. Cloud Claris ID tokens are valid for one hour. Cloud plans publish a 2 GB outbound Data API/OData transfer cap per user per month. Claris documents a first-party Claris MCP server reached at aiworkspace.platform.claris.com with a Claris ID. Opened MCP pages require FileMaker Server 22.0.2.204 or later, enabled Data API and OData, fmrest and fmodata privileges, and a Claris Studio team-manager account. Those pages do not document FileMaker Cloud as an MCP host. Generated tools cover per-table CRUD and per-script execution. The official fmsadmin CLI administers FileMaker Server from the host machine and is not supported on FileMaker Cloud. Connector catalogs were not opened. Computer-use viability is unassessed. API scores 7 and is the best path. MCP scores 6: official with useful table and script tools, but gated to current Server plus team-manager access. CLI scores 4 as a host-local admin tool.

Best path today: api · Overall automatability: 7/10