Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Review candidates and run hiring actions in InterviewFlowAI from Claude, ChatGPT, Codex and more.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.interviewflowai.com/mcpRun this in your terminal
claude mcp add --transport http interviewflowai https://api.interviewflowai.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"interviewflowai": {
"url": "https://api.interviewflowai.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"interviewflowai": {
"type": "http",
"url": "https://api.interviewflowai.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.interviewflowai.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain interviewflowai.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, FOGA node
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connect InterviewFlowAI to Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code, OpenCode, and other MCP-compatible AI agents. Ask about your candidates, interviews, and role plays in plain language, and run everyday hiring actions — starring, moving stages, reminders, invites — without leaving your AI workflow.
"Who are my top candidates for the Senior PM role, and where did each of them shine?"
"Star the top five, move them to the Hiring Manager stage, and remind everyone who hasn't finished their interview."
"Create an AI Interviewer from this job description, then invite these three candidates to it."
Ask a question like that in Claude or Codex, and the answer comes back from your own InterviewFlowAI workspace — not from a spreadsheet you pasted in ten minutes ago. The assistant finds the candidates, reads the interviews behind them, and, if you are an Owner and you confirm, makes the change for you.
InterviewFlowAI MCP is a hosted remote MCP server. You do not need to run anything locally, install a package, or manage a server. You connect your AI assistant to
https://api.interviewflowai.com/mcpand sign in with your InterviewFlowAI account.
https://api.interviewflowai.com/mcpcom.interviewflowai/mcpRecruiting teams already use AI assistants to write outreach, summarize notes, and prep for debriefs. The gap is data: the assistant does not know who applied, who finished an interview, or how anyone scored. So you copy and paste, and the assistant reasons about a stale fragment of your pipeline. Then you switch back to the dashboard to act on what it told you.
The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external systems through a consistent interface. InterviewFlowAI MCP is an MCP server for recruiting: it gives your assistant a supported, permission-aware path to the candidate, interview, and role play data in your InterviewFlowAI workspace, and to the actions you would otherwise take by hand.
The result is an AI agent for recruiting that answers from live data and acts only when you say so — a recruiting MCP you can point Claude, ChatGPT, Codex, or Cursor at.
Everything above, plus:
Every change starts as a preview. Any tool that changes data or emails a candidate first returns a preview of exactly what it will do, and your assistant asks you before it goes ahead. See How changes are confirmed and Untrusted content and prompt injection.
InterviewFlowAI MCP never decides on its own who advances. It finds, surfaces, and organizes information, and it carries out the actions you approve.
The server exposes the tools below. Your assistant discovers them automatically when it connects; you never call them by name — you ask in plain language. AI Interviewers are called *jobs* in tool names.
| Tool | What it does |
|---|---|
list_jobs | List and search AI Interviewers, with candidate counts. |
get_job | Read one AI Interviewer's full configuration. |
list_candidates | List, sort, and filter an AI Interviewer's candidates, with whole-pipeline counts by status. |
get_candidate | Read one candidate's interview, evaluation, and details. |
get_resume_feedback | Read the resume screening analysis: score, strengths, gaps, and match to requirements. |
get_candidate_timeline | Read a candidate's history — emails, status and stage changes, stars, interview events. |
list_stages | List your workspace's custom hiring stages. |
export_candidates | Export candidates to CSV and return a download link. |
get_export | Check on a large export and get its link when it is ready. |
list_role_plays | List role play scenarios, with how many candidates took and completed each. |
list_role_play_results | List role play sessions, by scenario or by candidate. |
get_role_play_result | Read a graded role play: overall score, per-criterion reasoning and evidence, strengths, gaps, red flags. |
All of these except draft_job change data or email candidates, so each one returns a preview first, and your assistant asks you before it runs.
| Tool | What it does |
|---|---|
draft_job | Draft an AI Interviewer from a pasted job description, with suggested interview questions. Saves nothing. |
create_job | Create an AI Interviewer, usually from a draft. |
clone_job | Copy an AI Interviewer with all its settings and questions. Candidates are not copied. |
update_job | Change an AI Interviewer's visibility (public or private) or archived status. |
star_candidates | Rate candidates 1–5 stars, or remove the rating. |
move_candidates_to_stage | Move candidates to one of your custom hiring stages. |
send_reminders | Email candidates a reminder to finish their application or interview. |
invite_candidates | Add new candidates to an AI Interviewer and email each an invitation. |
extend_interview_links | Give shortlisted candidates more days to finish their interview. |
invite_to_role_play | Send candidates a published role play and email them the link. |
update_candidate_notes | Replace a candidate's recruiter notes. |
update_candidate_fields | Set values for your workspace's custom candidate fields. |
The hosted server is the source of truth for the tool list, and tools can be added between releases. The official documentation describes the current capabilities.
These are the fastest way to confirm the connection works:
List my AI Interviewers.
Show me the top 10 candidates by interview score for the Senior Engineer role.
Who completed their interview for Sales Associate this week?
Of the candidates who scored above 70, which three would you look at first,
and what would you want to probe in a live call?
Why did this candidate get a low resume score? Show me their timeline too.
Across the candidates for this role, what are the most common weak spots?
Is that the candidates, or is it how the interview is asking the question?
Star the top 5 candidates for Senior Engineer and move them to the Onsite stage.
Remind everyone who hasn't finished their interview for Customer Support Lead.
Invite the shortlisted candidates to the customer-call role play,
and show me their results when they're done.
Create an AI Interviewer from this job description: …
Export the starred candidates for Account Executive as a CSV.
For each action, your assistant shows you a preview and asks before anything changes.
A larger, categorized set lives in [examples/recruiting-prompts.md](examples/recruiting-prompts.md), and end-to-end recruiting workflows in [examples/workflows.md](examples/workflows.md).
Recruiter
│ ▼ Claude / ChatGPT / Codex / Cursor / VS Code / OpenCode / any MCP client │ ▼ InterviewFlowAI MCP ── preview ─▶ you confirm ─▶ change applied │ ▼ InterviewFlowAI │ ▼ AI Interviewers + Candidates + Interviews + Role plays
In plain terms:
https://api.interviewflowai.com/mcp. Nothing to install or operate.Your assistant never gets blanket access to InterviewFlowAI. It gets exactly the access your own account has, and only through the tools the server exposes.
https://api.interviewflowai.com/mcp
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 with your InterviewFlowAI account, or an API key |
| Client registration | Automatic — no client ID or secret needed |
| Plans | Every paid InterviewFlowAI plan, and the 7-day free trial |
| Access | From your role: Owners read and write, Viewers read |
| Rate limit | 60 requests per minute per person |
| Hosting | Hosted by InterviewFlowAI — no local install |
The server implements standard MCP OAuth discovery, so most clients need nothing beyond the URL: they find the authorization server, register themselves, and walk you through sign-in in your browser.
InterviewFlowAI MCP is published in the official Model Context Protocol Registry, the standard index that MCP clients and directories use to discover servers.
com.interviewflowai/mcp
| Registry name | com.interviewflowai/mcp |
| Version | 1.1.0 |
| Transport | Streamable HTTP |
| Remote endpoint | https://api.interviewflowai.com/mcp |
The com.interviewflowai namespace is domain-verified, so the listing is published by InterviewFlowAI itself rather than by a third party.
You can query the live record directly:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.interviewflowai/mcp"
The manifest published to the registry is server.json in this repository. Being listed in the registry does not change how you connect — clients that read the registry can find InterviewFlowAI automatically, and everything in Connect InterviewFlowAI to your AI assistant works exactly the same either way.
This repository is documentation for people. If you are an AI agent reading it:
Only the beginning is shown; read the rest in the repo