Multi-stepAutomation
Let your AI pick up where it left off.
Use MCP to check a database revision, retrieve only new changes, and process updates without repeatedly downloading the whole table.
A complete worked example
Let the next agent session start at the last checkpoint.
A research agent has already processed a response table. It should inspect new changes without downloading every record again.
Fictional project and sample data. This preview does not submit, publish, or change access.
Authorized agent connection · illustrative result
Changes since the last run
A sample incremental check performed by an active connected agent.
- Checkpoint
- Previous successful revision
- Batch
- 3 changes to process
| Record | Change | Action |
|---|---|---|
| R21 | Completed | Include in the next summary |
| R09 | Draft updated | Wait for completion |
| R04 | Deleted | Remove its derived reference |
A safe stopping point
Read all pages of the change batch and handle deletion entries. Advance the durable cursor only when the intended processing completes; an external runner is needed for scheduled checks.
What the recipient can access
Only records and changes accessible to the current connection.
Kept out of this handoff
Other workspaces and records outside that access.
How it runs
- Check for a changeRead the database status and compare its revision with the last successfully processed cursor.
- Read only what changedPage through the change journal and fetch affected records. Handle deleted records using their tombstones.
- Save your placeAdvance the saved cursor only after the batch completes. Make processing safe to repeat after a retry.
- You getA small, repeatable polling routine that notices inserts, updates, and deletions while respecting the requesting user's current access.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Use Fermium MCP to check [database] for changes since my saved cursor. If unchanged, stop without loading rows. Otherwise page through all changes, fetch the affected records, and handle deletion tombstones. Summarize new completed responses separately from draft updates. Save the next cursor in an authorized project note only after processing succeeds. Make retries idempotent. Ask me what action to take on new responses before adding one.
What this workflow needs
A connected agent or external scheduler must run the checks. Fermium exposes the status and changes tools; this prompt does not create a continuously running agent.
Why use a cursor instead of a last-updated timestamp?
The database revision gives changes a stable order and includes deletion events. Timestamps remain useful for display, while a cursor supports reliable incremental processing.