AI Interview Agents MCP Server
Lets any MCP client drive the recruiting workflow in natural language: create roles, screen CVs, schedule and manage candidate interviews, and read back scored reports with transcripts.
README
AI Interview Agents — MCP Server
The official Model Context Protocol server for AI Interview Agents, a voice-AI hiring platform. It lets any MCP client (Claude, Cursor, custom agents) drive the recruiting workflow in natural language: create roles, screen CVs, schedule and manage candidate interviews, and read back scored reports with transcripts.
The live voice interview itself is out of scope here (that runs on a separate real-time service). This server triggers interviews and reads back the results.
What it exposes
- Roles — list your roles, or create one from a job description.
- Candidates & CVs — parse dropped CV/PDF files, normalize messy pasted candidate lists (names, emails, phone numbers, experience, skills), and reassign candidates between roles.
- Interviews — schedule interviews (with a
dry_runmode that normalizes and previews without sending anything or consuming quota), reschedule, cancel, and send reminders. - Reports — read the candidate pipeline and pull back scored interview reports with transcripts.
Use the hosted server (recommended)
The server runs remotely with OAuth sign-in. Point any Streamable-HTTP MCP client at:
{
"mcpServers": {
"ai-interview-agents": {
"type": "streamable-http",
"url": "https://mcp.aiinterviewagents.com/mcp"
}
}
}
Your client discovers the auth flow automatically via /.well-known/oauth-protected-resource and signs you in with your AI Interview Agents account. It is also listed in the official MCP Registry as com.aiinterviewagents/interviews.
Run it locally (stdio)
pip install -e .
export AIIA_FIREBASE_TOKEN="<your token>" # or: aiia-mcp login
aiia-mcp
AIIA_BACKEND_URL overrides the API base if you are pointing at your own deployment.
How auth works
The server holds no account secrets. Each request carries the user's own Firebase ID token, forwarded to the backend as a bearer token — the same trust path as the web app. For the hosted transport, an OAuth layer (dynamic client registration + PKCE) bridges MCP clients to Firebase sign-in.
Development
pip install -e ".[dev]"
pytest
ruff check .
License
MIT — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.