Resume vs Calendar — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Resume vs Calendar
In-depth architectural comparison of the Resume and Calendar MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Resume
Workplace & Productivity · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Calendar
Workplace & Productivity · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Resume if you need specialized Workplace & Productivity tools running via a local process. Choose Calendar if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
R
Choose Resume when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Store the facts every output is built from: name, email, phone, location, links, summary, skills, roles with bullets, education, certifications, languages. One profile per data directory; Pro adds named variants
profile_get
Return the stored profile as JSON, exactly as the other tools see it
resume_create
Write the resume as `.docx`. Bullets are ranked by keyword hits and recency, then trimmed to `max_pages` against a measured word budget; matched keywords are bolded, missing ones are reported and never added. Styles: `modern`, `classic`, `compact
cover_letter_create
A one-page letter in four parts -- opening, fit, proof, close -- drawn only from the profile. Tones: `formal`, `direct`, `warm`. Unknowns come back as `[add: ...]` prompts
tailor_to_job
Gap analysis against a posting: the keywords it actually asks for, which of them your profile already covers, which it does not, a coverage figure, and rewrites that only reorder facts you already stated
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Resume is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Calendar belongs to Workplace & Productivity using local stdio subprocess. Select Resume when you need capabilities focused on workplace & productivity and Calendar when you require tools for workplace & productivity.
Read an existing resume `.docx` back into the profile shape, section by heading. Best effort; nothing is saved unless `save: true
resume_to_markdown
The resume as markdown, for an application form or an ATS box
resume_to_html
Printable HTML with a print stylesheet. Open it and print to PDF
license_status
Show free or Pro mode
license_activate
Activate a Pro key (verified offline)
Calendar Tools (11)
ics_import
Read a `.ics` file (`path`), pasted contents (`text`) or a public feed (`url`, Pro) and keep it locally under a name. Importing the same name again replaces it.
calendars_list
Every imported calendar: name, source, event count, size, when it was imported.
events_list
Every event between two dates with recurring series expanded to real occurrences, sorted, in your own time zone. Each row carries an id.
events_search
Events whose title, description, location, organizer or attendees contain a phrase.
free_busy
Merged busy blocks and the free gaps inside your working hours, day by day. Events marked free/transparent do not count as busy.
conflicts
Every pair of events that overlap, with the overlap in minutes -- across all calendars, so a client call clashing with a school run is caught. A longer window is shortened to the free 31 days and answered, never refused.
next_event
The next thing that has not started, and how long until it does.
event_export
Write chosen events (by id, or a whole window) to a new `.ics` you can send. Times in UTC, so it lands correctly in any client.
event_to_time_entry
Turn one meeting into the exact arguments for the time-tracker's `entry_add`, so a call becomes billable time without retyping it.
Turn your CV facts into a tailored Word resume and a cover letter that invents nothing: keyword matching against the posting, page-fit trimming, and bracketed prompts wherever a fact is missing. Everything stays on your machine.
Read the .ics your calendar already exports: what is on this week, when you are actually free, what is double-booked, and turn a meeting into billable time. All local.