Resume MCP Server vs Google Workspace MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Resume MCP Server vs Google Workspace MCP
In-depth architectural comparison of the Resume MCP Server and Google Workspace MCP 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 MCP Server
Workplace & Productivity · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Google Workspace MCP
Workplace & Productivity · Local stdio
Quality: 67/100 (Great) | Auth: OAuth 2.0
Verdict Summary: Choose Resume MCP Server if you need specialized Workplace & Productivity tools running via a local process. Choose Google Workspace MCP 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?
Choose Resume MCP Server 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).
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_OAUTH_REDIRECT_URI, WORKSPACE_MCP_LOG_LEVEL, WORKSPACE_MCP_PORT, WORKSPACE_MCP_HOST.
MCP server for searching and retrieving structured information from local resume and job application documents (.docx, .pdf, .md, .txt) with auto hot-reload. 21 tools for full-text search and filtering by skill, company, and education, plus structured extraction of work experience, achievements, badge skills, and side projects. pip install resume-mcp-server
Comprehensive Google Workspace MCP server with full support for Google Calendar, Drive, Gmail, and Docs, Forms, Chats, Slides and Sheets over stdio, Streamable HTTP and SSE transports.
Category & Scope
Tools & Capabilities Breakdown
Resume MCP Server Tools (19)
list_resume_summaries
List resumes as lightweight identity records — id, name, email, phone only.
Use this to orient and pick a resume_id before fetching details with other tools.
Much more token-efficient than list_resumes when you only need to identify who is present.
Pass query to filter by first or last name (absorbs the old search_resumes_by_name tool).
Response includes total_count and items for pagination.
get_resume_profile
Get a resume's top-level fields (contact info, professional statement, education)
without the nested work experience and badge skill lists.
See also: get_resume_full for everything about this resume in one call.
Returns {"error": ...} if resume_id is not found.
get_resume_full
Get a resume's complete nested structure in one call: profile fields plus all
work experiences (with achievements), badge skills, side projects (with technologies),
and education entries (with competencies).
Prefer get_resume_profile plus the scoped list_* tools (list_work_experiences,
list_skills, list_side_projects, list_education) when you only need part of this —
it's more token-efficient. Use get_resume_full when you need the whole picture at once.
Returns {"error": ...} if resume_id is not found.
list_resumes
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 MCP Server is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Google Workspace MCP belongs to Workplace & Productivity using local stdio subprocess. Select Resume MCP Server when you need capabilities focused on workplace & productivity and Google Workspace MCP when you require tools for workplace & productivity.
List all documents. When doc_type is 'resume' (or omitted), structured resume data
is returned if available; otherwise flat file metadata is returned.
Response includes total_count and items for pagination.
See also: list_resume_summaries for a lighter-weight, more token-efficient listing;
get_resume_full for one resume's full nested structure by resume_id.
get_resume
Return the full extracted text of a document, as {"text": "..."}.
Note: takes a file path (see list_resumes), not a resume_id — use get_resume_profile
or list_resumes to fetch structured data by resume_id instead.
Returns {"error": ...} if path is not found.
search_resumes
Search across all documents for a keyword or phrase.
Response includes total_count, items, has_more, next_offset, and message for pagination.
search_resumes_by_skill
Find which resumes list one or more given badge skills. Returns resume identity and matched
skill names only — more token-efficient than list_resumes when filtering by skill.
Accepts either a single skill string or a list of skills to filter by multiple at once.
Each result includes: id, first_name, last_name, matched_skills.
Response includes total_count, items, has_more, next_offset, and message for pagination.
list_work_experiences
List work experiences, optionally filtered to a specific resume, only current roles,
and/or a keyword query matched against company name, position title, or achievement
descriptions (absorbs the old search_work_experiences tool).
Each result includes a resume_id field identifying which resume the experience belongs to.
Response includes total_count and items for pagination.
Returns {"error": ...} if resume_id is given but not found.
get_work_experience
Get a single work experience entry with its achievements.
Returns {"error": ...} if id is not found.
list_achievements
List achievements (resume bullet points), optionally filtered to a specific resume
and/or a keyword query matched against the achievement text (absorbs the old
search_achievements tool).
Response shape depends on the arguments given, to keep the common case cheap:
- resume_id given, query omitted: bare {id, desc} per item (cheapest — you already
know which resume these belong to).
- query given, and/or resume_id omitted: each item also includes company_name,
position_title, work_experience_id, and resume_id, since that context would
otherwise be unrecoverable from the achievement alone.
Response includes total_count and items for pagination.
Returns {"error": ...} if resume_id is given but not found.
get_achievement
Get a single achievement (phrase skill) by ID.
Returns {"error": ...} if id is not found.
list_skills
List badge skills (technologies, tools, languages), optionally filtered to a resume
and/or a keyword query matched against the skill title (absorbs the old search_skills tool).
Note: badge skills are deduplicated and shared across resumes by title, so — unlike
work experiences, side projects, and education — items here do not carry a resume_id.
Response includes total_count and items for pagination.
Returns {"error": ...} if resume_id is given but not found.
+7 more tools listed on main page
Google Workspace MCP Tools (123)
start_google_auth
Manually initiate Google OAuth authentication flow.
NOTE: This is a legacy OAuth 2.0 tool and is disabled when OAuth 2.1 is enabled.
The authentication system automatically handles credential checks and prompts for
authentication when needed. Only use this tool if:
1. You need to re-authenticate with different credentials
2. You want to proactively authenticate before using other tools
3. The automatic authentication flow failed and you need to retry
In most cases, simply try calling the Google Workspace tool you need - it will
automatically handle authentication if required.
search_gmail_messages
Searches messages in a user's Gmail account based on a query.
Returns both Message IDs and Thread IDs for each found message, along with Gmail web interface links for manual verification.
Supports pagination via page_token parameter.
get_gmail_message_content
Retrieves the full content (subject, sender, recipients, body) of a specific Gmail message.
Bodies are returned inline and truncated at 20,000 characters. Set full=True to
get the complete, untruncated message instead: it is exported to disk and the
response carries a short-lived download URL (HTTP transport) or file path (stdio
transport) rather than the body, so large messages never stream through the model
context. Stateless deployments have no file storage, so there full=True returns the
untruncated body inline.
get_gmail_messages_content_batch
Retrieves the content of multiple Gmail messages in a single batch request.
Supports up to 25 messages per batch to prevent SSL connection exhaustion.
get_gmail_attachment_content
Downloads an email attachment and saves it to local disk.
In stdio mode, returns the local file path for direct access.
In HTTP mode, returns a temporary download URL (valid for 1 hour).
May re-fetch message metadata to resolve filename and MIME type.
send_gmail_message
Sends an email using the user's Gmail account. Supports new emails, replies, and
forwards, with optional attachments. Supports Gmail's "Send As" feature to send
from configured alias addresses.
To forward an existing message, pass forward_message_id. The original subject,
body (quoted with a "Forwarded message" header), and attachments are carried over.
In forward mode, body (if any) is prepended as a note and subject is optional.
Threading, reply, and signature options do not apply when forwarding.
THIS TOOL SENDS IMMEDIATELY AND CANNOT SCHEDULE. Gmail's REST API exposes no
send-time parameter; Schedule send is a web-UI feature with no API equivalent,
so no argument to this tool can defer delivery. Never tell a user a message
was scheduled. For "prepare now, deliver later", create a draft with
draft_gmail_message. An external scheduler must retain the message data to
create and send a new message via send_gmail_message at the chosen time, or
call users.drafts.send with the draft ID returned by draft_gmail_message.
Alternatively, let the user schedule that draft in the Gmail UI.
draft_gmail_message
Creates a draft email in the user's Gmail account. Supports both new drafts and reply drafts with optional attachments.
Supports Gmail's "Send As" feature to draft from configured alias addresses.
SCHEDULED SEND IS NOT AVAILABLE. Gmail's REST API exposes no send-time
parameter; the Schedule send feature is web-UI only, and a message cannot be
placed in the Scheduled folder through the API. Do not claim a message was
scheduled. To deliver at a chosen time, create a draft with
draft_gmail_message. An external scheduler must retain the message data to
create and send a new message via send_gmail_message then, or call
users.drafts.send with the draft ID returned by draft_gmail_message.
Alternatively, let the user schedule the draft in the Gmail UI.
get_gmail_thread_content
Retrieves the complete content of a Gmail conversation thread, including all messages.
Optionally also returns structured ownership analysis so a caller can
determine who sent the last message and who owes whom a response without
re-parsing the formatted string or making a second tool call.
get_gmail_threads_content_batch
Retrieves the content of multiple Gmail threads in a single batch request.
Supports up to 25 threads per batch to prevent SSL connection exhaustion.
list_gmail_labels
Lists labels in the user's Gmail account.
manage_gmail_label
Manages Gmail labels: create, update, or delete labels.
list_gmail_filters
Lists all Gmail filters configured in the user's mailbox.