careerproof-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub token for higher API rate limits / private repos | |
| CAREERPROOF_DB_PATH | No | Path to the local SQLite database | ./data/careerproof.db |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| careerproof_add_candidate_profileA | Registers a candidate's CV (Markdown or plain text) and extracts individually-citable claims from it. Every extracted claim is stored with confidence 'user_claim' — it is what the candidate says about themselves, not independently verified. |
| careerproof_index_repositoryB | Indexes a public (or token-accessible) GitHub repository: recent commits, pull requests, README/architecture docs, and dependency manifests. Everything pulled directly from GitHub is stored as 'verified' evidence because it is directly observed, not inferred. |
| careerproof_add_project_evidenceA | Manually attaches an evidence item to an indexed project (e.g. an architecture decision explained in conversation). Defaults to 'inferred' confidence since it wasn't pulled directly from a verifiable source. |
| careerproof_find_evidenceA | Free-text search across all stored evidence (commits, pull requests, docs, dependency manifests, CV claims and manual notes). Every result carries its confidence tag (verified / inferred / user_claim / missing) so the caller knows how much to trust it. |
| careerproof_analyse_job_descriptionA | Stores a pasted job description and extracts structured requirements (skills, tools, competencies) using bullet parsing and a curated keyword dictionary. No LLM is used here — the connected client can add further reasoning on top of these structured requirements. |
| careerproof_match_requirementsB | Scores every requirement extracted for a job against all stored evidence (indexed repositories and/or CV claims), returning a match strength (strong / moderate / weak / unproven) plus the specific evidence cited for each requirement. |
| careerproof_find_evidence_gapsA | Re-runs requirement matching for a job and returns only the requirements with weak or unproven support, each with a concrete suggestion for what evidence to add. |
| careerproof_generate_star_answerA | Builds a Situation/Task/Action/Result outline for a competency and project, scaffolded entirely from stored evidence (commits, PRs, docs). Never invents narrative detail: gaps are listed explicitly in 'missing_information' rather than filled in. The connected client should turn this outline into flowing prose. |
| careerproof_generate_interview_questionsB | Generates likely interview questions from a job's requirements, prioritising requirements with the weakest evidence so preparation time is spent where it matters most. |
| careerproof_score_interview_answerA | Rule-based (non-LLM) check of a candidate's practice answer: STAR structure presence, first-person action verbs, measurable results, length vs. a target word count, and keyword relevance to the target competency. Returns a score and specific, actionable feedback rather than a black-box grade. |
| careerproof_export_preparation_packB | Assembles the complete evidence-backed preparation pack for a job: requirement matches, evidence gaps, and generated interview questions. Returns either JSON or a Markdown report. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| prepare_for_interview | End-to-end preparation workflow: analyse a job description, match it to evidence, and surface gaps. |
| create_star_answer | Generates a cited STAR-answer outline for a competency and project, then asks for it to be turned into prose. |
| challenge_cv_claim | Interrogates a specific CV claim and checks whether repository evidence actually backs it up. |
| run_mock_technical_interview | Runs a short mock interview using generated questions and scores each answer against stored evidence. |
| identify_portfolio_gaps | Reviews all indexed projects and evidence to identify what kinds of projects or documentation would most strengthen the candidate's portfolio. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| candidate-profile | The most recently added candidate profile, including extracted CV claims. |
| skills-matrix | Aggregated technologies detected across every indexed project. |
TDQS
Scored across 11 tools
Each tool has a clearly distinct role: evidence ingestion (profile, repository, manual), analysis (job description, matching, gaps, scoring), generation (STAR, questions), and export. Potential confusion between find_evidence, find_evidence_gaps, and match_requirements is resolved by descriptions specifying search vs. gap-only vs. scoring. No two tools appear interchangeable.
All 11 tools use a consistent `careerproof_` prefix followed by snake_case verb_noun construction (add_, index_, score_, export_, find_, analyse_, match_, generate_). The pattern is predictable and readable. Only minor variance is verb choice (analyse vs. analyze) but not inconsistent.
11 tools is well-scoped for a career-evidence preparation server, covering ingestion, analysis, generation, and export without obvious bloat. Each tool earns its place by handling a distinct workflow step. Falls squarely within the ideal 3-15 range.
Core lifecycle is covered: ingest evidence (CV, repo, manual), analyze job requirements, match against evidence, identify gaps, generate answers/questions, and export a pack. Minor gaps exist for updating/deleting evidence items or profiles, but these are not critical for the stated prep workflow. Agent can work around via re-ingestion or new evidence.