google-calendar-mcp
Skill0 starsChanged 2 months agoMITView on GitHub
Create, list, update, and delete Google Calendar events via the Cursor Google Calendar MCP plugin. Use when the user asks for a calendar reminder, event, appointment, or to schedule something on Google Calendar.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/automate-before-manual.mdcCursor rule
- .cursor/rules/finish-task-dev-server.mdcCursor rule
- brainstormingSkill
- caveman-commitSkill
- find-skillsSkill
- semantic-versionSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- writing-plansSkill
- ask-before-architectureSkill
- automate-before-manualSkill
- caveman-commitSkill
- diagrams-mermaidSkill
- dont-be-lazySkill
- dont-forgetSkill
- find-jobSkill
- finish-with-dev-serverSkill
- init-fmzSkill
- instagram-chrome-postSkill
- project-initSkill
- recapSkill
- semantic-versionSkill
- skills-sh-maintainerSkill
- ui-change-e2eSkill
- validate-before-shareSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 83
Put a copy-paste Cursor prompt in description so the user can reopen the chat task on that day:
- Very specific: line 94
Prefer timeZone + ISO 8601 startTime/endTime over guessing offsets.
- Distinctive: line 98
If MCP returns auth errors:
- Very specific: line 101
Do not store OAuth tokens in the repo or ../secrets/.
- Distinctive: line 110
Commit calendar event IDs as project config (ephemeral per user).
- Distinctive: line 111
Ask the user to create events manually if MCP is connected and authenticated.
- Distinctive: line 112
Use browser automation for Calendar when MCP works.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Google Calendar (MCP)
Manage Faruk's Google Calendar through the Cursor Google Calendar plugin MCP — no Python scripts or extra OAuth setup when the plugin is already connected.
MCP namespace
| Item | Value |
| Namespace | plugin-google-calendar-google-calendar |
| Auth | OAuth via Cursor plugin (user signs in once in Cursor) |
| Default calendar | primary (farukz@gmail.com) |
Discover tools first: GetDynamicTools with namespace: plugin-google-calendar-google-calendar.
Available tools
| Tool | Use |
list_calendars | List calendars and IDs |
list_events | Events in a time range |
get_event | Verify or read one event by ID |
create_event | New event or reminder |
update_event | Change title, time, description |
delete_event | Remove event |
suggest_time | Find free slots |
respond_to_event | Accept / decline invitations |
Workflow — reminder or event
- Parse intent — title, date/time, all-day vs timed, timezone, optional agent prompt in description.
- Call
GetDynamicToolsforcreate_eventschema (required:summary,startTime,endTime). - Invoke via
CallDynamicTool:- Namespace:
plugin-google-calendar-google-calendar - Tool:
create_event
- Namespace:
- Verify with
get_eventusing returnedid. - Report
summary, date,htmlLink, and reminder settings to the user.
create_event patterns
All-day reminder (check something on a date)
{
"summary": "Short title",
"description": "Context + optional Cursor prompt for that day.",
"allDay": true,
"startTime": "2026-09-29",
"endTime": "2026-09-30",
"timeZone": "America/Los_Angeles",
"overrideReminders": [
{ "method": "popup", "minutes": 1440 },
{ "method": "popup", "minutes": 0 }
]
}- All-day
endTimeis the next calendar day (exclusive end). overrideReminders:minutes= how many minutes before the event.0= at start;1440= 24h before.
Timed meeting
{
"summary": "Meeting title",
"startTime": "2026-09-29T10:00:00-03:00",
"endTime": "2026-09-29T11:00:00-03:00",
"timeZone": "America/Sao_Paulo",
"addGoogleMeetUrl": true
}Description with agent prompt
Put a copy-paste Cursor prompt in description so the user can reopen the chat task on that day:
**Prompt para o agente (cole no Cursor):**
> Verifica o status do meu plano que expirou em 28/09/2026...Timezones
- User local:
America/Sao_Paulo(UTC-3). - US Pacific expiry times:
America/Los_Angeles(GMT-07:00). - Prefer
timeZone+ ISO 8601startTime/endTimeover guessing offsets.
Auth failures
If MCP returns auth errors:
- User must connect Google Calendar in Cursor Settings → MCP / Plugins.
- Do not store OAuth tokens in the repo or
../secrets/. - Escalate once for OAuth consent or 2FA — then stop.
Alternative (not default)
odyssey4me/google-calendar on skills.sh uses a Python CLI + local OAuth. Prefer this MCP skill when the Cursor plugin is available; use odyssey4me only when MCP is unavailable.
Do not
- Commit calendar event IDs as project config (ephemeral per user).
- Ask the user to create events manually if MCP is connected and authenticated.
- Use browser automation for Calendar when MCP works.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

