Async Interview

@async-interview list all active interview jobs and show me which ones have the most completed responses

Found 4 active interview jobs in your account. 'Senior Backend Engineer' has 12 completed responses (posted 8 days ago), 'Product Designer' has 7 responses (posted 5 days ago), 'DevOps Lead' has 3 responses (posted 2 days ago), and 'Frontend Developer' has 1 response (posted yesterday). The Backend Engineer role is seeing the strongest candidate engagement so far.

This example shows how the List Jobs tool surfaces your interview pipeline at a glance. The MCP returns job metadata including response counts, but you'll need to access the Async Interview dashboard to review actual candidate video responses. Requires read access to your organization's jobs.

@async-interview update the 'Product Designer' job to extend the application deadline by one week and change the title to 'Senior Product Designer'

Updated the job successfully. Title changed from 'Product Designer' to 'Senior Product Designer', and the application deadline has been extended from March 15 to March 22. The job URL remains the same, so existing links shared with candidates will still work. All 7 current responses are preserved.

The Update Job tool modifies job configuration without disrupting active applications. This is useful when you need to adjust requirements mid-campaign. Note that changing interview questions after candidates have responded may create inconsistent evaluation criteria—consider creating a new job instead for major question changes.

@async-interview delete the 'Frontend Developer' job since we filled that position internally, and confirm it won't affect our other active postings

Deleted the 'Frontend Developer' job (1 response on file). This action is permanent and the candidate response has been removed from your account. Your 3 remaining active jobs ('Senior Backend Engineer', 'Senior Product Designer', 'DevOps Lead') are unaffected and continue accepting applications.

The Delete Job tool permanently removes interview data, including all candidate video responses. Use this carefully—there's no undo. This example demonstrates the MCP's ability to clean up your job board after hiring decisions, but you should export any responses you want to keep before deletion. Requires write access to your organization.

When this MCP makes sense for lean hiring teams

A 10-person startup hiring two engineers per quarter can use this MCP to manage async video interviews without leaving Switchy. The three tools—list, update, delete—cover the full CRUD loop for interview jobs, so your hiring lead can check candidate progress, tweak questions mid-cycle, and archive closed roles in one workspace. This works if your team already uses Async Interview's platform and you're coordinating hiring in Switchy channels. The API key auth is straightforward. The trade-off: if you're running 20+ open roles or need candidate-facing features like scheduling or video playback, you'll still open the Async Interview dashboard. This MCP is for the hiring coordinator who wants job-level admin in Switchy, not a replacement for the full recruiting stack.

Using this MCP for post-sale video check-ins

A customer success team at a B2B SaaS company runs async video interviews with new enterprise customers to capture onboarding feedback. The MCP lets the CS ops lead list active interview jobs, update questions when a product feature changes, and delete completed jobs after synthesizing responses. This scenario works if your CS team treats these interviews like structured data collection, not one-off Loom requests. The three tools are enough for job-level management but won't surface individual responses or video transcripts—you'll still need the Async Interview UI for that. If your team runs fewer than five feedback cycles per month, the MCP overhead isn't worth it. This is for teams running repeatable interview workflows at scale, not ad-hoc customer calls.

When this MCP fits rotating research projects

A 6-person design agency runs user research sprints for three clients at a time, each with its own async interview job. The MCP gives the research lead a single place to list all active jobs, update prompts when a client pivots scope, and delete jobs when a project wraps. This works if your agency uses Async Interview as the standard research tool and you're coordinating projects in Switchy. The API key auth means one shared credential across the team. The limitation: the MCP doesn't expose candidate responses or analytics, so you'll still export data from the Async Interview dashboard for client deliverables. If your agency runs fewer than two research projects per month, managing jobs in the native UI is faster. This MCP pays off when you're juggling multiple concurrent interview workflows.