S3 Access-Key Auth for Syncs
S3 Access-Key Auth for Syncs
- S3 auth, two ways: cross-account assume-role (recommended, no long-lived keys leave your account) or an access key. S3-compatible stores (R2, Supabase, Backblaze) use access-key auth.
Same day: Sync Tools in the MCP Server, Syncs
Sync Tools in the MCP Server
- Available from the MCP server: 10 new sync tools ship in the hosted Captain MCP server (
captain_create_s3_sync/_r2_sync/_supabase_sync/_backblaze_sync, plus list/get/update/delete/reconcile/subscribe-webhook).
Syncs
- Keep a collection aligned with a cloud-storage bucket: a sync binds an S3-compatible bucket to a collection once, runs an initial backfill, then keeps the collection current as objects are added, changed, and removed. Create one with Set Up Sync; each store has its own create endpoint (S3, R2, Supabase, Backblaze).
- Two ways to stay current: scheduled reconciliation (
sync_interval_minutes, minimum 5) and optional real-time event webhooks for sub-minute propagation. Reconciliation is the backstop for any dropped event, and you can trigger one on demand with Reconcile. - Deletion propagation:
deletion_policycontrols what happens when an object leaves the bucket:mirror(remove from the collection),archive(keep the document but mark it archived, excluded from search by default, surfaced withinclude_archived: true), orignore. - Manage syncs: list, get, update (scope, schedule, deletion policy, pause/resume), and delete (stops the sync while indexed documents remain in the collection), provider-agnostic once a sync exists.