Career Compass MCP

Paste a job posting. Get an honest fit verdict.

Paste a job posting and your resume, and ask "Do I fit this?" You get a straight verdict (strong fit, stretch, or long shot), each of the posting's must-haves matched to evidence from your own background, and the top two gaps with how to handle them. Then Claude can tailor your résumé, write the cover letter and prep the interview without padding your history. Free, MIT-licensed, and in Claude Code and Cowork your files stay on your own computer.

Try it now

Just installed it and not sure what to type? Open a new chat and send whichever of these fits where you are. Each one works on its own in claude.ai chat, Cowork and Claude Code.

You have a job in mind. Send this, with your résumé and the posting pasted or attached underneath (a PDF is fine):

Here's my résumé and a job I'm considering. Do I fit this?

You only have your résumé.

Here's my résumé. What roles does it support today, and what would a screener skip?

You have neither at hand. See a full fit check on a made-up profile first, with nothing of yours shared. Open it in Claude, or send:

Show me a sample Career Compass fit check.

What a fit check looks like

A real run: the explore_opportunity output on the bundled sample data, and Claude's reply to it, trimmed for length (every cut is shown as "…"). Also as an MP4; how it was made is in docs/assets/demo/source.

Another example in text, on the same fictional Alex Rivera who ships with the package and a different made-up posting:

You:    [pastes a VP of Operations posting from a payments company]
        Do I fit this?

Claude: Stretch: strong on operations at scale, but no P&L or payments
        experience yet.

        Must-haves, with your evidence
        - 8+ years leading operations teams: Operations Manager at Apex
          Logistics, team of 42; Senior Program Manager at MedFlow, 6 PMs.
        - Scaling a process across sites: patient onboarding cut from 47 days
          to 11 across 3 acquired health systems.
        - Vendor and cost management: procurement cycle cut from 9 months to
          6 weeks; headcount costs down 18% while throughput rose 31%.

        Top two gaps
        1. P&L ownership. You ran $8M in program budgets, which isn't a P&L.
           Say what that budget covered, and ask in the screen whether the
           role owns a P&L from day one.
        2. Payments. Nothing in your history is payments or fintech. Lead
           with the healthcare compliance work as the closest thing, and
           don't claim more.

        Want me to tailor your résumé to this one, or track it?

The real reply goes on with talking points, red flags and questions to ask. A "day in the life" of the role comes only when you ask for one.

It won't pad your résumé

Every sentence it writes about you has to come from your history or from what you told it. When a stronger draft needs a fact it doesn't have, the draft says so in place:

- Cut patient onboarding from 47 days to 11 after the acquisition of 3
  regional health systems, leading a team of [confirm: team size] and
  eliminating $2.1M in compliance penalties over 18 months.

The sample record says what changed, not how many people did it, so the bullet asks. You fill in the bracket or cut it; nothing gets invented to sound stronger.

Get it in the Claude directory

In the Claude app or on claude.ai, open Customize → Plugins, search for Career Compass, and add it. That's the whole install.

The commands below work in Claude Code and Cowork. In claude.ai chat, just ask in plain words ("prep me for my interview on Friday").

A few things it does once you've used it for a while: saves end with a receipt of what changed, you can record an offer or how an interview round went, and /career-compass:today leads with a debrief the day after an interview. When you accept an offer it switches to closing out the search and then to your first weeks in the new job. If you want a nudge, you can set up a morning briefing on your own computer.

Turn your git history into honest résumé evidence

If you write code, you have a record of what you did. Ask:

"Look at my project in ~/code/billing-service and tell me what I can honestly claim on my résumé."

harvest_evidence reads that project's git history on your computer and reports counts, each with the command that produced it. It writes nothing and sends nothing.

## What is measurably true
- Committed to billing-service across 14 distinct months, 2024-11 to 2025-12.
  - how: git log --no-merges --author=<you> --since=2024-10-07; counted distinct YYYY-MM values.
- 212 of 530 non-merge commits in this window are yours (40%).
  - how: git rev-list --count --no-merges, with and without --author. Share of commits,
    which is a measure of participation and NOT of contribution size.

## What this cannot tell you
- Did any of this ship to real users, and did anything measurable change when it did?
  That number is the résumé line; none of the above is.

Example on made-up numbers. Counts are not achievements, so Claude asks the questions the log can't answer first. Say you built the invoicing service and it shipped, and the draft keeps to that:

- Built the invoicing service in billing-service over 14 months (212 commits),
  which [confirm: what changed for users once it shipped, and by how much?].

Tell me what it got wrong

There is no telemetry, so the only way I hear about a bad fit check is if you say so. Open a "What did your first fit check get wrong?" issue (leave out anything personal), or say what you used it for in Discussions.

More: How Career Compass works, with pages for people who were laid off, career switchers and new grads.

For other MCP clients