[Day 4 of 30] Full Context in One Place. Plan Better, Move Faster.
Connect calendar and inbox so your AI sees every meeting, thread, and task. One context, way more effective.
The situation
On Day 3 you connected your calendar so the AI sees your meetings and attendees. Your threads, plans, and the tasks that land in email still live only in the inbox. To have full context in one place, you add the inbox next. Then the AI sees everything that matters: meetings, who’s in them, who wrote what, what they asked for. From there it can help you plan your day, prep for the next meeting, and decide what to do next without you copying a single message or event. One chat, one context. That’s how you plan better and move faster. The step is simple: connect Gmail to the same environment where you already have the calendar.
This post continues the 1% Better series; if you have not read the first three posts, you can find them in the archive.
The 1% upgrade
Add a Gmail MCP next to your calendar MCP:
Use the same Google Cloud project as in Day 3.
Enable Gmail API.
Add the MCP to your config.
Sign in once in the browser.
The AI then has tools to read and manage your inbox (list, search, mark read, archive, reply, extract tasks, classify). Together with calendar, you get full context. For example:
“Plan my day using my calendar and unread email.”
“Prep me for my next meeting” (attendees plus recent threads with them).
“What should I do next?”
“Turn today’s emails into tasks.”
No pasting. One context. You plan and act from there.
Why calendar and email together
Calendar gives “when” and “who.” Email gives “what needs a response” and “what they asked for.” Combined, the AI has enough to triage, plan, and prep. You keep one inbox and one calendar; the system just reads them. You get speed and better decisions because the context is complete.
How to add the Gmail MCP
If you already have a Google Calendar MCP from Day 3 and used a Google Cloud project (Path B):
Enable Gmail API in the same project.
Go to Google Cloud Console and select the same project (e.g. the one where you enabled Calendar API).
APIs & Services -> Library. Search for Gmail API, open it, click Enable.
Add the Gmail MCP to your app.
In Cursor (MCP config):
In a new chat, ask: “Add the Gmail MCP to my MCP config. It should use the same OAuth credentials as my Google Calendar MCP (same project, same credentials.json path).” The agent will create or update your MCP config.
Restart Cursor so it loads the new Gmail MCP server.
In Claude Code (Connectors):
Open Settings, then Connectors.
Find Gmail and turn the connector on.
Open the Gmail connector to set tool permissions. You choose for each action (read email, search, create draft, etc.) whether Claude may always use it, must ask you first, or never use it. Read-only and write/delete tools are listed separately. Set this once; you can change it later in Settings -> Connectors -> Gmail.
First sign-in.
Restart the app fully. In Tools and MCP (Cursor) or Connectors (Claude Code), turn the Gmail server on.
In a new chat, ask: “Show my last 5 emails” or “How many unread emails do I have?”
A browser window will open for Google sign-in. Sign in and allow Gmail access. The token is saved; you won’t need to sign in again unless you revoke access.
Use it.
Ask “What’s unread?”, “Find emails from [name],” “Reply to this email: [text],” or “Extract tasks from these emails.” The AI will use the Gmail MCP tools.
If you use Apple Calendar (Path A from Day 3) and don’t have a Google Cloud project yet:
Follow the same sequence as in Day 3 (create project, OAuth consent screen, Desktop OAuth client, download credentials.json), but enable Gmail API in the Library instead of Calendar API. Then add the Gmail MCP and sign in once (steps 2–4 above).
Day 3 steps (use these, with “Gmail API” instead of “Calendar API”):
Google Cloud Console -> create a project (or pick an existing one).
APIs & Services -> Library -> search Gmail API -> Enable.
APIs & Services -> OAuth consent screen -> External (or Internal if workspace) -> add app name, support email, test users if needed -> Save.
APIs & Services -> Credentials -> Create credentials -> OAuth client ID -> Application type: Desktop app -> name it (e.g. “Gmail MCP”) -> Create -> download the JSON and save as credentials.json somewhere safe.
Add the Gmail MCP to your app (step 2 above: Cursor prompt or Claude Connectors), then First sign-in (step 3) and Use it (step 4).
What you can do with email and calendar together
Once both MCPs are connected, you can ask in natural language. Full list by category:
Email - read and scan
“Show my last 10 emails” / “What’s unread?” / “How many unread do I have?”
“List emails from this week” / “Open this email” / “What did they say in the last message from [person]?”
Email - search and find
“Find emails from [person]” / “Search for ‘invoice’ in subject” / “Emails about ‘contract’”
“Unread from last 7 days” / “Thread with [person] about [topic]”
Email - reply and send
“Reply to this email: [your text]” / “Draft a reply to the last email from [person]” / “Reply to all in this thread with: [text]”
Email - tasks and triage
“Extract tasks from these emails” / “Turn today’s emails into tasks” (then create tasks in your system)
“What do I need to do from this thread?” / “Which of these are urgent?” / “Classify my unread by priority”
Email - inbox management
“Apply smart filters to my inbox” (e.g. archive marketing, keep the rest)
“Archive these” / “Mark these as read” / “Add label ‘To answer’ to these”
“Clean my inbox” / “Archive newsletters, list what’s left” / “Inbox zero: mark read and archive everything that’s not actionable”
Calendar - today and next
“What’s on my calendar today?” / “Today’s schedule” / “What’s my next meeting?” / “When is my next call?”
“Who’s in my next meeting?” / “Attendees for my next event” / “When is my next free slot?”
Calendar - range and list
“Events this week” / “Meetings tomorrow” / “Next 7 days on work calendar”
“Which calendars do I have?” / “Use my work calendar”
Calendar - manage (if your Calendar MCP supports it)
“Cancel this meeting” / “Remove this event” / “Cancel the weekly standup series”
“Create a 30-min block tomorrow at 2pm”
Combined - email + calendar
“Plan my day using my calendar and unread email”
“Prep me for my next meeting” (attendees + recent threads with them)
“What should I do next?” (next meeting + unread + suggestions)
“End of day: what meetings did I have and what’s still unread?”
“Turn today’s emails into tasks and add ‘Prep for X meeting’ from my calendar”
“Reply to this email and block 30 min tomorrow to do it”
“Weekly review: summarize my meetings and email volume, suggest follow-ups”
Takeaway
Add a Gmail MCP next to your calendar MCP. Same OAuth project, one extra API (Gmail), one sign-in. After that, the AI has full context: your meetings, your threads, your tasks. Use it to plan your day, prep for meetings, and decide what to do next without pasting anything. One place, way more effective.
10-minute action
In your Google Cloud project (the one you use for Calendar), enable Gmail API (APIs & Services -> Library -> Gmail API -> Enable).
Add the Gmail MCP to your MCP config (or ask the AI to do it with the same credentials as Calendar). Restart the app.
Turn the Gmail server on, then in a new chat ask: “Show my last 5 emails” or “How many unread emails do I have?” Complete sign-in in the browser if prompted.
Try one combined use case: “What’s on my calendar today and how many unread emails do I have?” If you get real calendar events and a real count, both MCPs are working.
What to do next
Think about one thing you do often that mixes email, calendar, or both: a recurring ritual, a bottleneck, or something you wish were automated. Then ask your AI in an open way: e.g. “I want to [describe the outcome]. I have Gmail and Calendar connected. How could I do this with what we have, or what would we need to add?” You’ll get concrete steps or ideas to try. If you share what you asked and what worked (or didn’t), I can shape the next mini products around that.