Async interview MCP integration

No. The toolkit exposes four actions - List Interview Responses, List Jobs, Update Job, and Delete Job - and none of them creates an invitation or sends a message. Ayro reads and maintains jobs that already exist, while scheduling and candidate outreach stay in Async Interview itself.

No. Delete Job permanently removes an interview job and the toolkit has no restore action, so treat it as final. The safe pattern is to have Ayro read the job back through List Jobs and get a recruiter's confirmation before the delete call runs.

List Interview Responses returns responses together with candidate details, so Ayro handles applicant information whenever it reads that list. It reads through the credentials of the Async Interview account you connect, which means it sees exactly what that account is entitled to see and nothing beyond it.

A Zap runs a fixed sequence once a trigger matches. Ayro decides mid-conversation which of the four actions to call - listing responses, then updating or deleting the job based on what the recruiter says next - and can chain several of them in a single exchange.