Google Calendar MCP vs Outlook Personal MCP
A side-by-side look at the Google Calendar MCP and Outlook Personal MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Calendar MCP for workplace & productivity work as a local process; choose Outlook Personal 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 Google Calendar MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_CALENDAR_CLIENT_ID, GOOGLE_CALENDAR_CLIENT_SECRET, GOOGLE_CALENDAR_REFRESH_TOKEN. - You want tools like
auth_status, setup_instructions, set_client.
Choose Outlook Personal MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OUTLOOK_MCP_CLIENT_ID. - You want tools like
whoami, list_messages, search_messages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 61/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GOOGLE_CALENDAR_CLIENT_IDGOOGLE_CALENDAR_CLIENT_SECRETGOOGLE_CALENDAR_REFRESH_TOKEN | OUTLOOK_MCP_CLIENT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 19 | 32 |
| Full listing | View Google Calendar MCP | View Outlook Personal MCP |
Tools & capabilities
Google Calendar MCP tools 19
auth_statusShows whether this server is connected to Google: token presence and source (env variables or a stored in-chat login), expiry, the Google account email, granted vs missing OAuth scopes, where the credentials file lives and where the OAuth client comes from. Makes no network calls and never returns the token itself. Call it first when other tools report the server is not connected.setup_instructionsStep-by-step checklist for connecting this server to Google: creating a Google Cloud project and a Desktop-app OAuth client, publishing the consent screen (mandatory — Testing-mode refresh tokens die after 7 days), downloading the client JSON and handing its PATH to set_client. Works without any credentials; the checklist shortens to 'enable the API + log in' when an OAuth client is already configured (one client serves the whole mcp-google-* line). Never asks the user to paste secrets into the chat.set_clientSaves the OAuth client credentials from the JSON file downloaded from Google Cloud Console ('Download JSON' on a Desktop-app client). Pass the file PATH — the secret must never be pasted into the chat. The client is stored once in the shared ~/.config/mcp-google-auth/client.json (owner-only) and reused by every mcp-google-* server; tokens stay per-server. After this, call start_login.start_loginFirst step of connecting from the chat, without editing config files or restarting the client. Returns authorizeUrl — show it to the user as a clickable link and ask them to open it in the browser ON THIS MACHINE, pick the Google account and approve access. A one-shot listener on 127.0.0.1 catches Google's redirect; the code is exchanged locally and never passes through the chat. Does not open the browser itself. The attempt lives 10 minutes; when the browser shows the success page, call finish_login.finish_loginSecond step: confirms the browser consent finished, saves the tokens to an owner-only file and verifies the login with a read-only identity call, returning the account email and the granted scopes. After success every tool works immediately — no client restart. If the user granted only part of the requested permissions, the login is still saved and missingScopes lists what will not work. Logging in under a different Google account replaces the previous login (its refresh token is revoked best-effort) and the response carries previousAccountEmail so the change never goes unnoticed.logoutRevokes the stored token at Google (oauth2.googleapis.com/revoke) and deletes the local credentials file. Tokens supplied via env variables are NOT touched — remove them from the MCP client config manually; envTokenStillSet in the response says whether any are still in effect.list_calendarsLists the calendars on the user's calendar list: id (use it as calendar_id in every other tool), summary, description, timeZone (IANA), accessRole (owner/writer/reader/freeBusyReader — writes need writer or owner), primary:true on the main calendar, and hidden/selected flags. The special id "primary" always addresses the main calendar without listing first. Paginate with page_token from nextPageToken. Calendars shared with the user but never added to their list do not appear here — address them by their explicit id.get_calendarFetches one calendar-list entry: summary, description, timeZone (the calendar's default IANA zone — use it to interpret event times), accessRole, defaultReminders and primary. Works only for calendars on the user's list; for a shared calendar never added to the list, use raw_request with path calendar/v3/calendars/<id> instead.list_eventsLists events on a calendar: id, summary, start/end (all-day events carry date with an EXCLUSIVE end; timed events carry dateTime), status, attendees with responseStatus, organizer, recurrence, hangoutLink, eventType. time_min/time_max bound the window (an event overlapping the window is included). single_events=true expands recurring events into individual instances — required for order_by=start_time and the right choice for questions like "what is on my calendar this week"; without it recurring events appear once as the series master. time_zone only changes how times are RENDERED in the response, never the events themselves. q searches summary/description/location/attendees. updated_min + show_deleted enable incremental polling (cancelled events come back as status=cancelled). Paginate with page_token from nextPageToken.get_eventFetches one event by id: summary, description, location, start/end, attendees with their responseStatus (accepted/declined/tentative/needsAction), organizer, recurrence rules, recurringEventId (present on instances of a series), conferenceData/hangoutLink (Google Meet), reminders, visibility, transparency and eventType. Works for a series master and for an individual instance id alike.create_eventCreates an event and returns it (id, htmlLink, start/end, attendees, hangoutLink when add_meet). Times: EITHER start_date_time + end_date_time (RFC3339; add time_zone for recurring events) OR start_date + end_date for all-day (end_date is EXCLUSIVE — the day after the last day). recurrence makes it a recurring series. attendees invites guests — but the API sends invitation emails ONLY with send_updates=all (the default notifies nobody). add_meet attaches a Google Meet link (may come back status=pending — re-run get_event for the final URL). This is a plain calendar write: it does not check for conflicts — call query_free_busy first to find a free slot. Never blindly re-send after a timeout or 5xx: the event may already exist — check with list_events first, or you will create a duplicate and re-invite everyone.update_eventPartially updates an event (PATCH): only the provided fields change, but a provided nested object REPLACES its predecessor wholesale — attendees replaces the entire guest list (get_event first, send the complete new list), reminders replaces all overrides, and a time change should carry BOTH the new start and end (start_date_time + end_date_time, or start_date + end_date). To reschedule one occurrence of a recurring series, pass that instance's id (from list_event_instances) as event_id; passing the series master id changes every occurrence. Guests hear about the change only with send_updates=all. Also works to update Out of Office / Focus Time blocks. Returns the updated event.- +7 more on the listing page
Outlook Personal MCP tools 32
whoamiReturn the signed-in user's Microsoft account profilelist_messagesList messages (newest first); optionally filter by folder or unread-onlysearch_messagesFull-text search across the entire mailbox (Graph `$search`)get_messageGet a single message; optionally include the full bodylist_attachmentsList a message's attachments (id, name, size, content type)download_attachmentDownload an attachment to a path under `OUTLOOK_MCP_FILE_ROOT` (refuses to overwrite an existing file)send_mailSend an emailreplyReply to a message (`reply_all` to reply to everyone)forwardForward a message to recipients with an optional commentmove_messageMove a message to another foldercopy_messageCopy a message to another foldermark_readMark a message read or unread- +20 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.
Google Calendar MCP
{
"mcpServers": {
"google-calendar-mcp": {
"command": "npx",
"args": [
"-y",
"@a1-x-tech/mcp-google-calendar@latest"
],
"env": {
"GOOGLE_CALENDAR_CLIENT_ID": "YOUR_GOOGLE_CALENDAR_CLIENT_ID_HERE",
"GOOGLE_CALENDAR_CLIENT_SECRET": "YOUR_GOOGLE_CALENDAR_CLIENT_SECRET_HERE",
"GOOGLE_CALENDAR_REFRESH_TOKEN": "YOUR_GOOGLE_CALENDAR_REFRESH_TOKEN_HERE"
}
}
}
}
Outlook Personal MCP
{
"mcpServers": {
"outlook-personal-mcp": {
"command": "uvx",
"args": [
"mcp-outlook-personal"
],
"env": {
"OUTLOOK_MCP_CLIENT_ID": "YOUR_OUTLOOK_MCP_CLIENT_ID_HERE"
}
}
}
}
Frequently asked questions
Google Calendar MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Outlook Personal MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Google Calendar MCP for workplace & productivity work and Outlook Personal 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.
Google Calendar MCP has no declared pricing — check the project's own site. Outlook Personal MCP has no declared pricing — check the project's own site. 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 google-calendar-mcp and outlook-personal-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Calendar MCP has a quality signal of 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Outlook Personal MCP has 49/100 (Fair) with 2 views, 0 installs and 2 GitHub stars.