A signup-form change or an import leaves your member records drifting. Custom fields fill in three different ways. Metadata blobs disagree from one batch to the next. Login redirects point the wrong tier at the wrong page, and you find out when a member complains. The fixes are not hard, they are just spread across every member, and editing them one at a time in the dashboard is the kind of job that never gets to the top of the list.
Scratch pulls your member list down as files on your computer. Your AI reads and rewrites the custom fields, metadata, and redirects across the whole list, not a handful at a time. Every change comes back as a word-level diff next to the original, and nothing reaches Memberstack until you approve it, member by member. Plan connections and subscription status are never in play.
Scratch is the companion app to Whalesync. Whalesync keeps your tools in sync; Scratch is where you clean the member data up first, so what syncs out is already right.
What Scratch edits in Memberstack
- Member custom fields (text and rich text)
- Member metadata (free-form JSON)
- Login redirect URLs
- Member email addresses
How it works
- Scratch pulls your member list into files. Your Memberstack members come down to a folder on your laptop, one file per member, with their custom fields, metadata, and redirect URLs. Nothing touches the live site.
- Your AI edits the fields you point it at. Open the folder in the agent you already use. Try a prompt on a few members, then let it run across the whole list. Normalize the custom fields, standardize the metadata, fix the redirect drift between tiers. Member plan connections, subscription status, and Memberstack system fields stay read-only, so the agent edits the copy but cannot move them.
- You review every diff and publish. In the Scratch desktop app, each changed field shows next to the original, word by word. Approve what ships, and Scratch writes only the members you approved back through the Memberstack API.
What teams use it for
- Normalize custom fields after a signup form changes and the new and old answers stop matching.
- Standardize metadata across imports, so members from different batches read the same way.
- Fix login-redirect drift between member tiers, so each plan lands where it should.
- Tighten rich-text custom fields that members or admins filled in inconsistently.
- Reconcile member fields after a migration, so the source of truth lines up again.
- Roll back a member redirect or field change, per member, when it went wrong.
Why not let AI write straight to Memberstack?
A direct API write or an MCP server hands the AI the publish button straight to your live membership. There is no diff, no review queue, no rollback. One confident pass can rewrite a redirect URL across thousands of members and point a whole tier at a dead page, and you find out when the logins start failing. By the time you spot it, it is already live and the original value is often gone.
Scratch gives the AI the same access, but against a local copy of your member list. The write-back step is pulled out and handed to you. The agent can change anything in the copy, only you commit it, and Scratch writes back only the fields you changed, so plans, subscription status, and the fields you did not touch stay exactly as they were. Every member Scratch writes back is reversible on its own.
What's safe, and what's locked
Member plan connections, subscription status, and Memberstack system fields are read-only. They are stripped before write-back, so the agent cannot push them even if it edits the copy. You bring your own AI: Scratch holds no AI credentials and runs no model, so you sign into Claude, Claude Code, Codex, Cursor, Copilot, Cline, or Windsurf the way you already do. By default, nothing leaves your machine until you publish. Every published change is reversible per member. Optional Python validators, which the AI can author, flag edits that break a redirect URL or touch a field you protected, right next to the diff.
Questions Memberstack users ask
Can Scratch change a member's plan or subscription?
No. Plan connections and subscription status are read-only in Scratch. The agent edits a local copy, and those fields are stripped before write-back, so they never reach Memberstack even if the copy is edited. Scratch only writes back the custom fields, metadata, redirects, and email addresses you approve.
Will a bad login-redirect edit go live before I see it?
No. Every redirect change lands in local files first and shows next to the original as a word-level diff in the Scratch desktop app. You approve member by member, and Scratch writes only the members you approved back through the Memberstack API. A validator can also flag a malformed redirect URL before you approve it.
Does the AI get my members' data, or send it anywhere?
You bring your own AI and sign into it yourself. Scratch holds no AI credentials and runs no model. Your member files stay on your machine, and nothing leaves it until you publish the changes you approved.
Can I undo a change after it has written back to Memberstack?
Yes. Every member Scratch writes back is reversible on its own. Roll back one member or a whole run, and Scratch restores the original value for you to publish.
See it on your own Memberstack
Pull your member list into files and watch the AI clean up one field across every member, then publish only what you approve.