Memberspot MCP integration

One hour. Create Login Token generates a short-lived auto-login credential tied to the learner's UID, so if they do not use it inside that window Ayro can simply issue a fresh one on the next message rather than escalating a password problem.

Yes. Memberspot caps the progress endpoints at four requests per second, which covers both Get User Course Progress and List User Course Progress, and List Users carries the same ceiling. A conversation reads one learner at a time, so the limit only becomes relevant if bulk exports run against the same API key at once.

The toolkit does expose Delete Users plus a POST variant for clients that cannot send a DELETE body, and only accounts that already belong to your school are removed - unknown addresses are ignored. Deletion is not a good fit for an unattended conversation, so keep it behind a human review step and let Ayro handle the lookup and access actions.

A Zap runs one predefined sequence when an event matches. Ayro decides which Memberspot calls a request actually needs while the learner is still in the chat - finding the account, reading progress, then granting the offer - and hands the conversation to a human agent with the full history when the account does not look right.