Career Compass MCP vs Sheets MCP
A side-by-side look at the Career Compass MCP and Sheets MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Career Compass MCP for workplace & productivity work as a local process; choose Sheets MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Career Compass MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
explore_opportunity, research_company, tailor_resume.
Choose Sheets MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
google_accounts, find_spreadsheet, create_spreadsheet.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 65/100 · Great | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 36 |
| Directory activity | 0 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 19 | 29 |
| Full listing | View Career Compass MCP | View Sheets MCP |
Tools & capabilities
Career Compass MCP tools 19
explore_opportunityJudge 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.research_companySet 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.tailor_resumeWrite 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.generate_cover_letterDraft 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.answer_applicationAnswer 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.format_for_atsReformat 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.pipeline_viewRead 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.pipeline_addAdd 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.pipeline_updateUpdate 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.classify_emailRead 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.prepare_interviewPrep 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.interview_arcFor 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.- +7 more on the listing page
Sheets MCP tools 29
google_accountsManage the Google accounts Sheets MCP can use. list: show signed-in accounts and the default. add: sign in to a Google account (opens a browser sign-in; also use this when a sign-in has expired). remove: sign an account out and revoke access. set_default: choose the account used for new spreadsheets.find_spreadsheetFind a spreadsheet by name among the ones the user has opened or created with Sheets MCP before (the list is kept on their computer). Use it when the user names a sheet instead of pasting a link, e.g. "my budget sheet". It can't search the rest of their Google Drive: if nothing matches, ask for the link. Leave query empty to list the most recent.create_spreadsheetCreate a new Google Sheets spreadsheet.get_spreadsheet_infoGet a spreadsheet's title, tabs (sizes, frozen rows/cols), charts (ids, types, data ranges), named ranges, and the first few rows of each tab. Call this first to understand a sheet's layout.read_rangeRead cell contents from a range, or its formatting with mode "formats". Large ranges are truncated; use next_range to continue.read_rangesRead several ranges in one call, across any tabs. Faster than calling read_range repeatedly. Each range is truncated to its share of max_cells; use its next_range with read_range to continue.write_rangeWrite values and/or formulas starting at the top-left cell of the range. Input is parsed like typing into the UI (formulas, dates, percentages work). Previous contents are saved for undo_last. Returns any formula errors found after writing.fill_rangeFill cells from a source block, like dragging the fill handle or pasting onto a bigger selection: the source's formulas (relative references shift), values and formatting repeat across the destination. Use it after writing one row or column of formulas to extend them across a table, instead of sending every column. With continue_series, patterns continue instead (1, 2, 3 → 4, 5, 6; Jan → Feb; dates). The destination's previous contents are saved for undo_last. Returns any formula errors found after filling.append_rowsAppend rows after the last row of data in a table (detected from the given range or tab).clear_rangeClear values and formulas in a range (formatting is kept). Previous contents are saved for undo_last.find_replaceFind and replace text across a tab or the whole spreadsheet. Not undoable - consider read_range first.undo_lastUndo the most recent write_range, append_rows, or clear_range made through this server (restores values/formulas only, not formatting or structure). History is kept in memory until the server restarts.- +17 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Career Compass MCP
{
"mcpServers": {
"career-compass-mcp": {
"command": "npx",
"args": [
"-y",
"career-compass-mcp"
]
}
}
}
Sheets MCP
{
"mcpServers": {
"sheets-mcp": {
"command": "npx",
"args": [
"-y",
"@sheetsmcp/server"
]
}
}
}
Frequently asked questions
Career Compass MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Sheets MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Career Compass MCP for workplace & productivity work and Sheets MCP for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Career Compass MCP is listed as free. Auth: no auth required. Sheets MCP is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add career-compass-mcp and sheets-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Career Compass MCP has a quality signal of 65/100 (Great) with 0 views, 0 installs and 6 GitHub stars. Sheets MCP has 68/100 (Great) with 9 views, 0 installs and 36 GitHub stars.