Claris Future Features

Claris is getting into the Standby & Backup Feature Sets . . .

This is part three in this series - here's the link if you've not reviewed the first blog post - FileMaker Prevention and Maintenance.

We've entered 2026 with a raft of new features for the Claris Platform.

The end of 2025 saw the release of the Claris MCP (Model Context Protocol) in the context of allowing Developers and early adopters to review and test this feature set.

At the time of publishing this blog, these two features are still in ETS.

• AWS Backup Service

• FileMaker Standby Server

Both Features have been openly discussed by Rick Kalman from Claris.

MCP Server.

This feature - or Service or even Server - opens the door to allow Clients such as Claude Desktop to call Tools - CRUD Actions or scripts with Natural Language.

Think an API Call for the average user.

It's worth considering that these scripts and therefore the data from tables will require their own use 'context' and therefore written clearly - and probably exclusively - for MCP use.

AWS Backup Service.

This feature will arrive as part of a future update, some time in early 2026.

This has been described as an 'seem-less' function of the backups, just as the backs function of the Claris Cloud, which is hosted on the AWS Platform.

As stated in earlier blog posts, it's advisable to keep a duplicate of your backups to ensure no data is unique - especially backups.

Filemaker Standby Server.

This feature is expected to be introduced with the release of FileMaker Server 2026.

At any time, your Production Server can fail, and there needs to be a policy on how quickly a replacement Server can be enabled for Production.

Example: I'm currently within a project to build a solution for a client around their new Synology NAS to periodically create snapshots the LIVE FMS to the NAS - allowing for the NAS to host and serve as the FMS DR.

FileMaker Future Take Away.

These options - available now, or in the future - should form the back bone of your FileMaker Server Disaster Recovery (DR) policy . . .