We have set up OttoFMS and MCP Server and it all works well.
We are using Claude to chat to our FileMaker database.
When we do searches and request to perform data analysis all works well.
However, when we attempt to create a company or update the details of a company record OData service terminates abnormally and needs to be restarted manually. The record gets created and we get a response but then the next request returns a 502 error indicating and the logs show OData has terminated abnormally.
We are running latest version of FileMaker Server on Windows Server 2022
Using the new MCP Server option in OttoFMS so it’s a black box from that perspective. Had a look at the logs but can’t see any posts or patches.
The only thing the ottofms logs show is this
2026-04-11T23:30:04.453Z info start odata by OttoFMS API
2026-04-11T23:40:57.693Z error Error executing OData MCP tool ‘CreateCompany’: Failed to make OData call: 502 Bad Gateway -
IIS 10.0 Detailed Error - 502.3 - Bad Gateway
.....
and the FileMaker Server log shows
2026-04-12 09:40:06.681 +1000 Error 701 IFSTEST0322 OData Provider process has terminated abnormally.
Seems like i found the culprit.
The database was connected to Claris Studio and every time a record was created in company table it would attempt to sync it to Claris Studio automatically. This would cause the OData service to terminate.
I deleted the hub and data source however it still connected to the database and tried syncing.
So i deleted the Claris Studio in my database file and that fixed the issue.
Unfortunately, i now have a continuous flow of aythentication failed in the event log.
At least it is now working and OData is not crashing
