AI Interview Agents MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AI Interview Agents MCP ServerList all candidates for the senior developer role."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: job-search-mcp
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-mcpAIIA_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.
Maintenance
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dpkdhingra91/aiia-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server