{"report":{"v":1,"package":"career-compass-mcp","version":"2.16.1","ranAt":"2026-11-16T11:44:16.310Z","install":{"ok":true,"integrity":"sha512-iV0eUqVbCVp/k9mKGrzjrNey00vEBMQjbczZrPLT1vO39pgUktJQ1KEVf10zA+n+gnJbo/4KRdDfHOadKNeohw==","deps":96,"scripts":[],"bins":["career-compass-mcp"],"license":"MIT","engines":"node >=22.0.0","repository":"https://github.com/benskamps/career-compass-mcp.git","bin":"career-compass-mcp"},"start":{"ok":true,"ms":211,"serverName":"career-compass","serverVersion":"2.16.1","protocol":"2025-06-18","stderr":"Career Compass MCP server running on stdio\n"},"tools":[{"name":"explore_opportunity","description":"Judge how well the user fits one job posting, using their saved Career KB and stated preferences (salary floor, remote or relocation, notice period). Returns a verdict (Strong fit, Stretch, or Long shot) with a score, requirement-by-requirement evidence, the top gaps and how to address them, and talking points; if the user pastes the job board's own match label, it agrees or disagrees with it explicitly. Use it whenever the user pastes a posting and asks whether to apply. Before anything is saved, pass the résumé they pasted as `resume` and the verdict works from that. Writes nothing.","params":["posting","company","role","notes","sourceFitLabel","resume"]},{"name":"research_company","description":"Set up a research brief on a company the user is applying to or interviewing with: what it does, stage, culture, interview process, and how it fits the user's target roles. The server does not browse; it returns the brief's outline plus the user's targets, and you fill it from web search when you have it, citing sources. Without web search, the brief becomes a checklist of what to look up and where. Use explore_opportunity instead to judge fit for a specific posting.","params":["company","role","applicationId"]},{"name":"tailor_resume","description":"Write a résumé tailored to one job posting from the user's saved Career KB: the posting's vocabulary, the most relevant real achievements first, nothing invented, and [confirm: ...] placeholders where a fact is missing. Returns the résumé text first, then a keyword match report. Use it when the user wants a résumé for a specific posting. Before anything is saved, pass the résumé they pasted as `resume` and it tailors from that. Use format_for_ats afterwards for a specific applicant system's fields. Writes nothing.","params":["posting","format","pages","includeProjects","focusAreas","company","resume"]},{"name":"generate_cover_letter","description":"Draft a cover letter in the user's voice from their saved Career KB, built on real achievements that match the role and quoting their saved narrative (why they're looking, a gap, a switch) word for word. Use it when the user asks for a letter. Works from a pasted posting, from an application already in the pipeline (its cached posting, role, and notes), or from just a company and role. Company claims come only from the posting or the user. Before anything is saved, pass the résumé they pasted as `resume`. Writes nothing.","params":["posting","company","role","applicationId","hiringManager","tone","angle","resume"]},{"name":"answer_application","description":"Answer the questions on a job application form (why this company, years of experience with X, work authorization, salary expectation, start date, short essays) from the user's saved Career KB, each within its character or word limit. Eligibility answers come only from what the user saved or said; anything else is a [confirm: ...] placeholder, and a \"years with X\" the history can't support is flagged, never inflated. Use it whenever the user pastes application or screening questions. Before anything is saved, pass the résumé they pasted as `resume`. Writes nothing.","params":["questions","company","role","posting","resume"]},{"name":"format_for_ats","description":"Reformat résumé text the user already has into clean, parse-safe plain text for an applicant tracking system (Workday, Greenhouse, Lever, LinkedIn, iCIMS, Taleo, SmartRecruiters, or generic): standard headings, consistent dates, sections ready to paste field by field, and long sections flagged (limits vary by employer). Use it when the user is about to paste a résumé into an application form. Reformats only, never rewrites content; use tailor_resume to change what the résumé says. Writes nothing.","params":["resumeContent","targetSystem","postingUrl"]},{"name":"pipeline_view","description":"Read the job application pipeline. action \"next_actions\" answers \"what should I work on?\" with a ranked digest led by one start-here move; \"list\" shows applications (filter by status or priority); \"stats\" gives funnel and response rates, plus any pattern the user's own numbers support; \"get\" fetches one application by id; \"calendar\" returns upcoming interviews, follow-up dates and offer deadlines as .ics text for the user to save and open in their calendar. Read-only: never modifies anything, and the .ics is returned, not written.","params":["action","id","filterStatus","filterPriority","sortBy","limit"]},{"name":"pipeline_add","description":"Add one job application to the pipeline. Writes one new record; never modifies an existing one. If the same company and role are already tracked, it writes nothing and returns the existing id instead (use pipeline_update to change that one). Use this when the user applies to, or wants to track, a role not yet on the board. On the very first application, the result carries Career Compass's one-time offer of a morning briefing; pass it on as one optional line.","params":["company","role","status","postingUrl","postingText","source","referral","priority","excitement","salaryMin","salaryMax","dateApplied","allowDuplicate"]},{"name":"pipeline_update","description":"Update one application already in the pipeline: change its status, add a note, set a follow-up date, record a contact, log an interview round and its outcome, record an offer and its answer deadline, or note which résumé version was sent. Writes: overwrites the fields you supply and leaves the rest untouched. Use after the user confirms the change.","params":["id","status","priority","notes","followUpDue","contactName","contactTitle","contactEmail","interviewType","interviewDate","interviewers","roundOutcome","offerBaseSalary","offerBonus","offerEquity","offerCurrency","offerStartDate","offerExpiresDate","offerNotes","tailoredResumeVersion"]},{"name":"classify_email","description":"Read a job-search email the user pasted (recruiter outreach, interview invite, assessment, rejection, offer) and extract its type, company, role, contact, dates, urgency, and next action, matched against applications already in the pipeline, with a short reply draft. Writes nothing: any pipeline change it suggests goes through pipeline_update after the user agrees.","params":["emailContent","autoUpdatePipeline"]},{"name":"prepare_interview","description":"Prep the user for one upcoming interview: an opening pitch, STAR stories (saved ones from their story bank first, skipping any this company or interviewer already heard), likely questions for that round, questions to ask, and the concerns to get ahead of, quoting their saved narrative where it applies. Finds the application by id or company name and uses its posting, rounds, and contacts. For a later round in a process already under way, call interview_arc too so the prep doesn't repeat ground covered. Before anything is saved, pass the résumé they pasted as `resume`. Writes nothing.","params":["applicationId","company","role","interviewType","interviewerInfo","postingText","focusAreas","resume"]},{"name":"interview_arc","description":"For a user already partway through one company's interviews: reconstruct the process so far (rounds done, what each surfaced, threads left open, which saved stories each round already heard) from the pipeline, the journal, the story bank, and their notes, then project what the next round will probe and how to prepare without repeating covered ground. Use prepare_interview instead for a first interview. Writes nothing.","params":["applicationId","company","role","interviewSoFarNotes","nextRoundType"]},{"name":"evaluate_offer","description":"Analyze a job offer the user has received: total compensation year one and fully vested, how it compares to their current pay, stated targets, other offers (including live offers already recorded in their pipeline, side by side), and any market data they supply, then what to negotiate and the exact words. Use it when the user has an offer in hand. Benchmarks come only from data the user gives; the server never fetches salary data. Writes nothing; it ends by offering to record the offer and its deadline with pipeline_update, for the user's OK.","params":["applicationId","company","role","offerDetails","location","currentComp","marketData","priorities","otherOffers"]},{"name":"ingest_document","description":"Extract achievements, skills, and quotes from a career document the user pasted (performance review, award email, project summary, recommendation) as Career KB YAML for them to review, copying only what the document states and marking missing metrics [confirm: ...]. Extraction only: writing the reviewed YAML is a separate, explicit save_career_section call.","params":["content","documentType","associatedRole","associatedCompany","datePeriod"]},{"name":"generate_rejection_response","description":"Draft a short reply to a rejection the user received: keep the door open, ask for feedback, or decline politely, plus an alternative and a LinkedIn note. If you pass applicationId, this also sets that application's status to `rejected` in your pipeline — it does not only write a draft. Leave applicationId out when the user only wants the words.","params":["applicationId","company","role","rejectionContent","responseGoal","contactName","hadGoodRapport"]},{"name":"capture_insight","description":"Append one lasting takeaway to the user's career journal: what an interview surfaced, why an offer felt right or wrong, the pattern behind a rejection, or fresh proof of a skill. Later fit checks, interview prep, and résumés read these back. Writes one new entry and never changes existing ones. Offer it after a debrief, a rejection, or an offer decision, and save only with the user's OK. Set origin to user_said for what they said, or inferred for your own reading, which drafts then treat as a hypothesis.","params":["type","summary","detail","applicationId","company","role","signals","sentiment","source","origin"]},{"name":"save_career_section","description":"Write one section of the Career KB to disk. This is how the Career KB gets populated — ingest_document and the resume tools only read and extract. Replaces the whole section, so send the complete list you want stored, not just new entries. A save that would drop stored entries or achievements is refused and names them, unless `replace` is true. The previous version is kept as a timestamped .bak next to it. To undo a bad save, pass `restoreFrom` with a backup name that check_setup lists instead of `data`: the current file is backed up first, then that backup is put back. Writes to disk either way; use it only with the user's OK.","params":["section","data","restoreFrom","replace"]},{"name":"harvest_evidence","description":"Read a local project's git history and report what you measurably did there — months active, files and file types touched, your share of commits, test ratio — each with the command that produced it. Use it when the user cannot remember what they shipped, is writing a résumé bullet for a project, or needs proof of a skill. It reports counts and asks the questions a commit log cannot answer; it never invents achievements and never writes to the Career KB.","params":["projectPath","since","authorEmail"]},{"name":"check_setup","description":"Health-check this Career Compass install and report everything at once: how it is running (plugin or standalone) and its version, whether your data directory exists and is writable, which Career KB sections are filled in, the recent backups of each section with how to restore one, whether the pipeline file parses, leftover temp files, and whether the dashboard is running. Every finding that needs action comes with the one step that fixes it. Run it when something seems wrong, when the user asks whether it's working, or to find a backup to restore; not on first contact. Writes nothing.","params":["dashboardPort"]}],"toolsHash":"3ad998959ed852dc60d56e43bf1729be918be944001a98dad2fbe390294bc2de","wrote":[],"host":{"commit":"eaaffffaf52255d1b77dc4aacffdfaf353f0c12c","run":"https://github.com/itsHaddad/bragproof/actions/runs/43857070216"},"network":{"names":["registry.npmjs.org"],"conns":[]}},"summary":{"outcome":"started","needs":[],"contacts":[],"flags":[],"tools":19,"wrote":0,"callsTried":0,"callsAnswered":0,"callContacts":[]},"history":[{"package":"career-compass-mcp","version":"2.16.1","ranAt":"2026-11-16T11:44:16.310Z","outcome":"started","tools":19,"contacts":0,"flags":0,"serious":0,"toolsHash":"3ad998959ed852dc60d56e43bf1729be918be944001a98dad2fbe390294bc2de"}],"page":"https://bragproof.smaverk.com/r/career-compass-mcp"}