Skip to main content
Glama

interview-prep-mcp

CI PyPI Python License: MIT

An open-source Python MCP server for AI-assisted interview preparation. Runs in any MCP-compatible host — Claude Desktop, Cursor, Google Antigravity, Windsurf — and defaults to Google Gemini with optional OpenRouter for cross-provider model selection.

What it does

interview-prep-mcp exposes 17 tools that cover the full interview-prep loop:

  • Parse a job posting (URL or pasted text) and a CV (PDF or markdown).

  • Persist company and interviewer research collected by the host's other MCPs (e.g. firecrawl, exa) — this server doesn't scrape itself.

  • Generate personalized interview questions using the active LLM.

  • Submit practice answers and get scored evaluations.

  • Analyze weak areas across your practice history.

It also exposes:

  • A interview-prep://interviews/{id} resource bundling the full prep state for one session.

  • Two MCP prompts: daily_prep and mock_interview.

Related MCP server: Aurai Advisor (上级顾问 MCP)

Install

The fastest way — no global pip install:

uvx interview-prep-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "interview-prep": {
      "command": "uvx",
      "args": ["interview-prep-mcp"],
      "env": {
        "GEMINI_API_KEY": "AIza...",
        "OPENROUTER_API_KEY": "sk-or-..."
      }
    }
  }
}

OPENROUTER_API_KEY is optional — leave it out if you only want to use Gemini.

Google Antigravity

Antigravity uses the same mcpServers JSON in its MCP settings panel. Paste the same block as above. Antigravity ships with Gemini already configured at the host level, so you'll typically only need to add the MCP entry itself.

Cursor (~/.cursor/mcp.json)

Same mcpServers block as Claude Desktop.

Windsurf and other MCP-compatible hosts

Same mcpServers block; just paste it into whichever config path the host documents.

Required env

Variable

Required?

Purpose

GEMINI_API_KEY

Yes (default)

Direct Gemini API access.

OPENROUTER_API_KEY

No

Enables set_model to switch to any of 200+ OpenRouter models.

You can run with only one of them set. If neither is set, the server still starts — context tools (parsing, storage) work; smart tools will return a clear "no LLM provider configured" error when invoked.

To research companies and interviewers, install these alongside:

The host orchestrates all three. interview-prep-mcp exposes save_research_note for the host to persist whatever those companion MCPs returned.

Quick start (5 minutes)

  1. Set GEMINI_API_KEY and install the server in your host (see snippets above).

  2. In a fresh chat: parse_job_posting("https://example.com/jobs/123").

  3. parse_cv("/path/to/cv.pdf") — first CV becomes active automatically.

  4. start_interview_prep("Acme", "Senior Backend Engineer", job_id=1, cv_id=1).

  5. (Optional) Ask Claude to research the company via firecrawl/exa and call save_research_note(interview_id=1, kind="company", content="...").

  6. generate_questions(interview_id=1, count=10, types=["technical","behavioral"]).

  7. Answer questions; each answer goes to submit_practice_answer.

  8. After several answers: analyze_weak_areas(interview_id=1).

Tool reference

Tool

LLM?

Description

parse_job_posting(source_or_text, is_html?)

no

URL or text → structured JobPosting.

parse_cv(file_path)

no

PDF/markdown → CVProfile. First CV is set active.

list_cv_profiles()

no

All CVs with their is_active flag.

set_active_cv(cv_id)

no

Switch which CV other tools default to.

match_cv_to_job(job_id, cv_id?)

yes

Score + strengths + gaps.

start_interview_prep(company, role, job_id?, cv_id?)

no

New prep session.

list_interviews()

no

Active prep sessions.

save_research_note(interview_id, kind, content, subject?, source_url?)

no

Persist markdown research. kind ∈ {company, interviewer, other}.

get_research(interview_id)

no

Grouped by kind.

generate_questions(interview_id, count, types)

yes

Personalized Qs using job + cv + research.

list_questions(interview_id)

no

Previously generated.

submit_practice_answer(question_id, answer_text)

yes

Returns evaluation.

get_practice_history(interview_id)

no

Past attempts.

analyze_weak_areas(interview_id)

yes

Recurring gaps + recommended topics.

list_models(provider?, ...filters)

no

Gemini (curated) + OpenRouter (24h cached).

set_model(model_id, provider?)

no

Persist active model.

get_active_model()

no

Current selection.

Architecture

MCP Host
├── firecrawl-mcp ──────┐
├── exa-mcp ────────────┤
└── interview-prep-mcp ─┘
        │
        ├── Tools layer
        ├── Service layer (parsers + storage + LLM router)
        ├── SQLite (~/.interview-prep/db.sqlite)
        ├── Config (~/.interview-prep/config.json)
        └── LLM router ──┬── Gemini (default)
                         └── OpenRouter (optional)

The MCP composes with companion MCPs — it does not scrape itself. The host's Claude calls firecrawl/exa, then feeds findings into save_research_note.

Contributing

git clone https://github.com/shenmali/Interview-MCP-First
cd interview-prep-mcp
python3.11 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest
ruff check .
mypy interview_prep_mcp

CI runs ruff + mypy + pytest on every PR.

License

MIT — see LICENSE.

Available Tools

17 tools
analyze_weak_areas_toolC

Summarize recurring gaps across practice sessions; recommends focus topics.

Inputs: interview_id (required). Returns: object

generate_questions_toolC

Generate count interview questions using job + cv + research as context.

Inputs: interview_id (required), count (required), types (required). Returns: result

get_active_model_toolA

Return the currently active model (provider + id) or None.

Inputs: no named parameters. Returns: result

get_practice_history_toolC

Return all practice sessions for an interview.

Inputs: interview_id (required). Returns: result

get_research_toolA

Return all research notes for an interview, grouped by kind.

Inputs: interview_id (required). Returns: object

list_cv_profiles_toolA

List all CVs with their is_active flag.

Inputs: no named parameters. Returns: result

list_interviews_toolA

Return all active interview prep sessions.

Inputs: no named parameters. Returns: result

list_models_toolC

List available models. Provider 'all' merges Gemini + OpenRouter (top 20).

Inputs: provider, min_context, supports_json_only, free_only, +1 more. Returns: result

list_questions_toolC

Return previously generated questions for an interview.

Inputs: interview_id (required). Returns: result

match_cv_to_job_toolB

Match a CV against a job posting. Returns score (0-100), strengths, gaps, summary.

Inputs: job_id (required), cv_id. Returns: object

parse_cv_toolB

Parse a CV from a PDF or markdown file path. First CV becomes active automatically.

Inputs: file_path (required). Returns: object

parse_job_posting_toolA

Parse a job posting from a URL, raw HTML, or pasted text. Returns id + parsed fields.

Inputs: source_or_text (required), is_html. Returns: object

save_research_note_toolC

Persist a research note for a prep session. Markdown content is fine.

Inputs: interview_id (required), kind (required), content (required), subject, +1 more. Returns: object

set_active_cv_toolB

Switch which CV other tools default to.

Inputs: cv_id (required). Returns: object

set_model_toolC

Set the active model (persists to config). Requires the matching API key.

Inputs: model_id (required), provider. Returns: object

start_interview_prep_toolC

Create a new interview prep session and return its id + metadata.

Inputs: company (required), role (required), job_id, cv_id. Returns: object

submit_practice_answer_toolC

Submit an answer; returns evaluation (score + strengths + gaps + suggestion).

Inputs: question_id (required), answer_text (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct operation: CV parsing vs job parsing, question generation vs answer submission, session management vs research notes. No two tools have overlapping purposes; even similar verbs like 'list' and 'get' are applied to different resources (interviews vs practice history vs questions).

    Naming Consistency5/5

    All tools follow a consistent verb_noun_tool pattern in snake_case (e.g., parse_cv_tool, list_interviews_tool, set_active_cv_tool). Verbs are descriptive and uniformly placed at the start. No mixing of conventions or cryptic abbreviations.

    Tool Count5/5

    17 tools is well-scoped for a specialized interview preparation server. The count covers essential workflows (CV management, job parsing, question generation, practice, feedback, research, model config) without being overwhelming or sparse.

    Completeness4/5

    Core CRUD-like operations are present for key entities (create/list for interviews, parse/list for CVs and jobs, generate/list for questions). Minor gaps: no update or delete tools for CVs, job postings, or research notes, but the primary workflow (parse-match-practice-analyze) is fully covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers