sync

com.gemmein/mcp · Verify this server

Does what `npx gemmein sync` does, for an AI app with no terminal: takes the gemmein/ files' contents (path → text) and Gemmein applies them to Development through the same doors and validators — collections, payments, relays, AI tools and aliases, email templates, the app's name. The files win: what Development holds for each file sent is replaced, and the answer shows what changed first. A file not sent is left as it is (never deleted). plan: true shows the diff and changes nothing. Refusals come back per file with the fix. Writes to Development only; the server refuses Live changes here — request_live_action handles those. One call carries up to 1 MB of files in all; a bigger set goes in more than one call. File paths are the gemmein/ project files: gemmein/gemmein.config.json, gemmein/collections/<name>.json, gemmein/payments.json, gemmein/relays/<name>.json, gemmein/ai/tools/<name>.json, gemmein/ai/aliases.json, gemmein/emails/<name>.html, gemmein/emails/sign-in.json — the same formats the guide teaches. A founder may call this saving or applying their changes.