MAGFAST INTERNAL RESOURCE
Key point
Attentive has confirmed they have a closed beta MCP program built for AI agents including Claude and ChatGPT. It supports campaign draft creation and segment management. We've requested access — their Growth Strategy team will follow up directly.
What we're trying to do
When MAGFAST needs to line up and send a set of SMS/RCS messages, having Claude handle that directly via MCP would remove a lot of manual work — and spare the team from relying on Attentive’s difficult interface.
Claude could draft, configure, and schedule campaigns based on our direction, without someone having to build each one by hand in Attentive.
The alternative approaches — Zapier or an MCP-as-a-service connector — remain options if Attentive's native beta isn't available to us.
Beta access requested with Attentive on Jun 24, 2026. Mahyar from White Glove Support confirmed the program exists on Jun 25 and escalated our request to the Growth Strategy team for evaluation.
We are waiting to hear back. In parallel, two MCP-as-a-service candidates have been identified.
Attentive closed beta MCP
This is the list of project workspaces. Main is the shared source branch; the other names are separate workspaces that can later merge back into main.
commercemcp.com
This shows what the selected branch has changed. A page appearing here means that page has edits in the selected branch.
https://commercemcp.com
viasocket.com/mcp/attentive
Framer can place you in a branch automatically when edits are being isolated from main. If the current branch is not main, your edits are going into that branch until you switch or merge.
https://viasocket.com/mcp/attentive
Zapier
Framer can place you in a branch automatically when edits are being isolated from main. If the current branch is not main, your edits are going into that branch until you switch or merge.
About Attentive's closed beta
From Mahyar, White Glove Support (Jun 25, 2026):
Is manual/auto personal?
No. It is shared for the branch/site. The most recent setting change wins for everyone who uses that branch.
If two branches edit the same thing, who wins?
The branch that merges later is the one that can overwrite the earlier result, especially if both changed the same page, text, component, or setting. Merge order matters.
What if one person has two branches?
Treat them like two separate teammates. Each branch has its own snapshot and changes. If both touch the same thing, whichever branch is merged later can change what the first branch already put into main.
How should I think about overwrites?
Branches do not magically combine intent. If two branches change different pages, they usually merge cleanly. If they change the same object, page, or site setting, review carefully before and after merging.
How can branches save publishing steps?
With auto publishing on main, the team can review on a branch preview, merge when approved, and let that merge ship the update. That removes the separate “remember to publish” step.
When is manual still safer?
Use manual if the team often merges work before final approval, needs a scheduled release moment, or wants one last publishing gate after multiple branches land.
Pause and check what those branches are for. The small avatar/icon next to each branch usually indicates the person associated with that branch, often the creator or most recent person working there. If one already contains the work area you need, switch to it or coordinate with that person. If your edit is unrelated, create your own branch. Avoid editing main unless the change is tiny, safe, and clearly ready to ship.
Should I ever edit a branch I didn’t create?
It’s not automatically rude, but surprise-editing someone else’s branch is risky. Treat a branch like someone’s workspace: ask first, leave a note, or make your own branch unless you were invited to help, it is clearly a shared branch, or you are making a tiny urgent fix. The polite rule is simple: don’t change another person’s branch in a way that could change their plan without checking with them.