Choose a productivity MCP connection around one job: finding a free meeting slot, collecting overdue tasks, or locating a project note. A directory category or star count cannot establish that a server works with your account.
This guide was checked against publisher documentation on September 10, 2026. The examples are documentation-based; this update does not claim a completed installation or authenticated test.
Pick the app that already holds your data
| Your task | Starting point | Setup to investigate |
|---|---|---|
| Check Google Calendar availability | nspady/google-calendar-mcp, a community implementation | Google Cloud project, Calendar API, desktop OAuth credentials |
| Review and organize tasks | Todoist's official MCP documentation | Hosted endpoint and supported authentication |
| Find notes and project pages | Notion's official MCP setup | Hosted connection and workspace authorization |
These are different operating models. The Google Calendar project's README documents a local server and OAuth setup; it is not a Google-published integration. Todoist and Notion document hosted options. Choose one specific publisher before copying configuration: several unrelated packages can use the same app name.
Set up a calendar connection without guessing a package
For the linked community Google Calendar implementation, follow its README to enable the Calendar API, create desktop OAuth credentials, and configure the credentials file path. Its current npm identifier is @cocal/google-calendar-mcp; older articles may show another name. The README also describes authenticating before the first calendar call and reauthentication for credentials in test mode. Use its current installation section as the source of truth. Publisher instructions.
For the first request, specify the calendar, date range, and timezone:
Read my work calendar for tomorrow in America/Chicago. Show event titles and start times. Do not change anything.
Compare the result with the calendar app. Then try a request that depends on that data, such as finding a thirty-minute gap. A plausible-sounding answer without a visible tool result is not a successful connection check.
Add tasks or notes only when the workflow needs them
Once calendar reading works, decide whether a second connection solves a concrete problem. One useful sequence is reading tomorrow's events, reading open tasks, and drafting a plan. Review the draft before requesting any calendar or task changes.
For notes, use a page you can find yourself as the initial check. Ask for its title and link, then compare both with the source app. This catches wrong-workspace authorization and ambiguous search results early.
Keep a short setup record: publisher URL, client, selected account, permissions, and the date of your successful check. Browse productivity servers when you need another integration, or use the Cursor setup guide for client configuration. Avoid connecting every app simply because a server exists.
Adam Bush
Gus Marquez