MCP Recipe
Plan the week with Google Calendar and Notion
Influzer starter recipe: read the next seven days from Google Calendar, pull priorities from a Notion database, and draft a realistic weekly plan you can paste back into Notion.
MCP servers used
Compatible clients (author-reported, not verified by Influzer): Cursor, Claude Desktop, ChatGPT
Prerequisites
- Google Calendar remote MCP with access to the calendars you care about
- Notion remote MCP with access to a tasks/projects database
- Agreement on working hours and which Notion database is source of truth
Required permissions
Both connectors can read (and potentially write) personal productivity data after OAuth. Start read-only: ask the agent to draft the plan before creating or editing Notion pages.
Setup
Add Google Calendar (https://calendarmcp.googleapis.com/mcp/v1) and Notion (https://mcp.notion.com/mcp) as remote MCPs. Complete OAuth for both and confirm the agent can list upcoming events and query your tasks database.
{
"mcpServers": {
"google-calendar": {
"url": "https://calendarmcp.googleapis.com/mcp/v1"
},
"notion": {
"url": "https://mcp.notion.com/mcp"
}
}
}
Using Google Calendar, list my events for the next 7 days.
Using Notion, list open tasks/priorities from my main tasks database (ask me for the database name if unclear).
Draft a realistic weekly plan that protects 2 deep-work blocks on lighter days.
Do not create or edit Notion pages or calendar events until I approve the draft.
Expected result
A day-by-day plan that respects existing meetings and surfaces the top Notion priorities that still fit.
Sample output
Week plan
Mon: deep work 9–12 on Launch checklist (Notion); standup 10:30…
Risks: Thu is meeting-heavy — move writing block to Tue AM.
Troubleshooting
- Calendar empty: confirm the correct Google account and calendar are authorized
- Notion misses pages: share the database with the Notion integration / re-authorize
https://mcp.notion.com/mcp - Refuse bulk deletes or mass reschedules unless you explicitly ask