hashgraph-online/awesome-codex-plugins / plugins/colibird-ai/local-mcp-releases/skills/local-mcp-calendar
local-mcp-calendar
VerifiedUse when the user wants to check their calendar, find availability, or create/update/delete events in Apple Calendar on macOS. Powered by LMCP's Calendar tools, which are macOS-only.
Calendar & scheduling via LMCP
LMCP reads and writes the Mac's Calendar app (Calendar.app: local, iCloud and other accounts added
to it). These tools exist only on macOS; for a Microsoft 365 calendar, use m365_list_events /
m365_create_event (macOS and Windows, require connect_m365_account).
Core tools
list_calendar_names— the user's calendars (Personal, Work, …).list_calendar_events— events in a date range (defaults to today + 7 days); setevent_idto read one event in full.create_calendar_event— new event (title, start, end, optional location/notes/calendar).update_calendar_event/delete_calendar_event— modify or remove an event byevent_id; both takeconfirmand require the user's approval before applying.
Good practice
- For "am I free Tuesday?", list events for that day and report gaps.
- Always confirm the calendar + exact times before creating.
- Use ISO datetimes (e.g.
2026-07-01T10:00:00). - Destructive ops (update/delete) are confirm-gated — show the user what will change, get approval, then call with
confirm=true.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |