The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the InterviewFlowAI listing page.
Connect InterviewFlowAI to Claude, ChatGPT, Codex, and other MCP-compatible AI assistants. Ask about your candidates and interviews in plain language, and perform supported recruiting actions without leaving your AI workflow.
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 answers the question you actually had.
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.
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 and interview data already in your InterviewFlowAI workspace.
The result is an AI agent for recruiting that answers from live data — a recruiting MCP you can point Claude, ChatGPT, or Codex at.
With read access (mcp:read), a connected assistant can:
With write access (mcp:write, workspace Owners only), a connected assistant can:
That is the supported surface. InterviewFlowAI MCP does not screen, rank, reject, or advance anyone on its own — it finds, surfaces, and organizes information so a recruiter can decide.
A note on tool names. This repository documents capabilities rather than individual tool names, because the exact tool list is defined by the hosted server and can change between releases. Your assistant discovers the current tools automatically when it connects. See the official documentation for the authoritative capability list.
Those three are deliberately simple — they are the fastest way to confirm the connection works. Once it does, you can ask for the retrieval and the thinking in one question:
A larger, categorized set lives in examples/recruiting-prompts.md, and end-to-end recruiting workflows in examples/workflows.md.
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 supported tools the server exposes.
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1, using your InterviewFlowAI account |
| Scopes | mcp:read, mcp:write |
| 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 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.
| Registry name | com.interviewflowai/mcp |
| Version | 1.0.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:
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.
Pick your client below. In every case the only value you need is the endpoint URL, and authentication happens in your browser.
Setup steps for MCP clients change frequently. The commands below follow each vendor's current documentation, but if a client has changed its syntax, that vendor's own MCP documentation is the source of truth.
Then authenticate:
Select interviewflowai and complete the browser sign-in. To make the server available across all your projects rather than just the current one, add --scope user.
Reference: Claude Code MCP documentation
InterviewFlowAI) and the URL https://api.interviewflowai.com/mcp.Add the server to ~/.codex/config.toml:
Then authenticate:
Reference: Codex MCP documentation
Open Settings → MCP servers → Add server, choose Streamable HTTP, enter https://api.interviewflowai.com/mcp, and complete the sign-in. Codex IDE and desktop read the same ~/.codex/config.toml, so a server added through the CLI shows up there too. Restart the application after adding it.
InterviewFlowAI can be added to ChatGPT as a custom connector using the same endpoint URL. Connector availability depends on your ChatGPT plan and workspace settings — see the InterviewFlowAI MCP documentation for current setup steps.
Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect. Point it at:
Most clients will discover the authorization server automatically and prompt you to sign in.
You authenticate with your own InterviewFlowAI account, using the same email address you sign in to InterviewFlowAI with. Authentication uses OAuth 2.1 through InterviewFlowAI's identity provider, and the sign-in happens in your browser — you do not paste an API key into your AI client, and your password is never handled by the client.
Your session determines two things:
Access is expressed as two OAuth scopes:
| Scope | What it grants |
|---|---|
mcp:read | List and inspect AI Interviewers and Candidates, and review supported interview information. |
mcp:write | Update supported candidate fields. Available to workspace Owners only. |
If you only ever want to ask questions, connect with mcp:read alone. Read-only is a sound place to start, and you can add write access later.
Never share credentials with anyone, and never paste tokens into a public GitHub issue, a shared document, or a chat with an untrusted party. If you believe a token has been exposed, see SECURITY.md.
| Capability | Read | Write |
|---|---|---|
| List and inspect supported Candidates | ✓ | |
| List and inspect supported AI Interviewers | ✓ | |
| Review supported interview information and scores | ✓ | |
| Summarize supported candidate and interview context | ✓ | |
| Update candidate notes | ✓ | |
| Update candidate custom fields | ✓ | |
| Update candidate visibility | ✓ | |
| Update candidate archived status | ✓ |
An assistant can never exceed the permissions of the person who signed in. If you cannot do something in InterviewFlowAI, your assistant cannot do it either.
| examples/recruiting-prompts.md | A categorized prompt library — candidate discovery, interview completion, scoring, review, summaries, operations, and notes. |
| examples/workflows.md | End-to-end recruiting workflows, each with a goal, prompt, what MCP does, and the human review step. |
| examples/README.md | How to use these examples once you are connected. |
Do I need to run or host anything? No. InterviewFlowAI MCP is a hosted remote MCP server. You connect your client to the endpoint and sign in.
Is this an open-source MCP server? No. This repository holds documentation, examples, and configuration resources. The InterviewFlowAI MCP service itself is a hosted InterviewFlowAI product and its implementation is not published here.
Can my assistant see other companies' candidates? No. Your session is scoped to your own InterviewFlowAI workspace.
Can it reject or advance candidates automatically? No. The supported write capabilities cover candidate notes, custom fields, visibility, and archived status. Screening and hiring decisions stay with your team.
Which AI assistants are supported? Claude (Code and Desktop), ChatGPT, and Codex (CLI, IDE, and desktop), plus other MCP-compatible clients that support remote servers with OAuth.
Something is missing or wrong in these docs. Open an issue — see Contributing below.
Connect InterviewFlowAI MCP → Official MCP documentation
Learn about InterviewFlowAI MCP → MCP product page
Learn how AI agents can be used in recruiting → AI Agent for Recruiting
Learn about InterviewFlowAI → interviewflowai.com
Issues are welcome for documentation corrections, unclear setup steps, and MCP capability requests.
Do not include candidate information, customer data, personal data, authentication tokens, or any other credentials in a public issue. Issues in this repository are visible to everyone on the internet. Describe the problem in general terms and redact identifiers.
For security issues, do not open a public issue — follow SECURITY.md instead.
The contents of this repository — documentation, examples, and configuration resources — are released under the MIT License.
The InterviewFlowAI MCP service itself is a hosted InterviewFlowAI product. This repository provides documentation, examples, and configuration resources and does not contain the proprietary server implementation.
The MIT license applies to the files in this repository only. It does not apply to the hosted InterviewFlowAI MCP service, the InterviewFlowAI platform, or the InterviewFlowAI name and logo. Use of the hosted service is governed by your agreement with InterviewFlowAI.