Skip to main content
Glama
681,082 tools. Updated 2026-10-20 12:26

"Setting up Calendar and Reminders on Mac" matching MCP tools:

  • Start a new VolunteerReminder account for a human, using their email address. This does NOT finish signup and does NOT return an API key: it emails the person a verification link they must click to activate the account. Nothing can be built on the account and no reminders can ever send until they verify — and even then a new account starts in safe `test` mode (reminders reach only the owner, never volunteers) until a human turns on live sending from the dashboard. Idempotent: calling it again with the same email re-sends the link and creates no duplicate. After the user tells you they've verified, they mint an API key from the dashboard and reconnect this connector with it. Tell the user to check their email.
    ConnectorNo auth
  • Lists the lists (folders) in Apple Reminders (Reminders.app) on this Mac. Every answer carries as_of (when the list snapshot was read) and cache_age_seconds; if cache_age_seconds is above 0 the snapshot is that many seconds old and a list created since then may be missing — call again to force a re-read. For Microsoft To Do use todo_get_folders instead.
    ConnectorOAuth
  • List care-recipients — other people this account can send reminders to. Needed to get the recipient_id for create_reminder. Consent status matters: only "confirmed" recipients receive calls; "pending" means they haven't accepted the verification call yet, so reminders to them will be blocked.
    ConnectorNo auth
  • Marks a Microsoft To Do task as complete. It works through Apple Reminders, which syncs with To Do when the Microsoft account is added to Reminders, so the change appears in To Do after the next sync. Prefer task_id from todo_list_tasks. With `title` instead, it completes the one open task whose title contains that text (case-insensitive); if several match, it completes NONE and lists them with their task_id. Without `list` it searches every Reminders list, not only the To Do ones. Called without confirm it returns a preview; pass confirm=true to complete.
    ConnectorOAuth
  • A FEATURE FINDER, NOT A RECORD SEARCH. It searches Taokeh's own SCREENS, FEATURES and SETTINGS — never the books. Use it to tell the user WHERE in Taokeh to do something or change a setting: it returns the exact page(s) and what each one does, grounded in Taokeh's LIVE feature catalogue, so you never guess or invent navigation. ⛔ It does NOT look up documents, invoices, customers, products or any other RECORD, and it cannot tell you it failed to — a document number, a customer's DO/PO number, a person's name or an amount typed in here will still rank some page (the closest-worded screen), and that page will be a wrong answer wearing a right one's clothes. Records live elsewhere: search_documents (invoices, credit notes, quotes, delivery orders, bills, POs — and a customer's own Ref No), search_expenses (posted paid expenses), search_journal (ledger entries), resolve_customer / resolve_vendor / resolve_product (a named party or item), open_invoices (what one customer owes). Give a natural-language `query` about a CAPABILITY ("where do I turn on payment reminders", "how do I connect Shopee", "where's the SST setting") and it ranks the real features and hands back the top matches, each with the page's absolute deep-link URL(s), a one-line description of what the page does, an optional configHint (Taokeh keeps a feature's options on its OWN page, not in a global Settings menu), and an addOn flag (a paid add-on this company may not have). It GUIDES to the UI only — it changes nothing: no setting is ever toggled by the connector, that stays a human action in-app. If nothing matches it says so honestly — then tell the user to browse the left sidebar or contact support; never make up a path.
    ConnectorOAuth
  • Read VolunteerReminder's public plan catalog: each plan's monthly and annual price (USD), volunteer limit, and included features (SMS reminders are included with no per-message credits or metering). No API key required — use this to help a user comparison-shop or decide which plan fits before they sign up.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • MCP connector for Apple Reminders — search, create, complete, and edit via your own Mac.

  • Outlook.com, Microsoft 365, Google calendars: free time, events, invitations, booking pages, polls.

  • Use this when the member asks to create, host, plan or set up a PUBLIC event that others attend ('host an event', 'set up a meetup', 'create an event page for X'). Creates ONE hosted event on Connections - its own public page with RSVPs and tickets - as a draft, in the workspace this connection is bound to; a draft is private until published. It does not put anything on the member's own calendar: for 'add it to my calendar', a meeting, an appointment or blocked-out time, use connections_calendar_add. Pass dry_run:true first to see exactly what would be created without creating anything, and show that to the member before writing for real. Every other setting - tickets, registration questions, capacity, approval, the cover, and later changes to any of these - goes through events_manage_hosted_events (create-event / update-event) with the event's id.
    Connector
    Destructive
    OAuth
  • Ask Pally, the user's personal assistant, to do or answer something. Use it for anything that needs the user's messages, email, calendar, contacts, reminders, memory, phone calls, bookings, or purchases. When the user talks to Pally, send their words unchanged and present Pally's reply verbatim as your entire response. When you hand Pally a task, write it in plain words with every detail the user gave, and use the reply in your answer. If Pally is still working, call check_pally with the returned turn_id.
    ConnectorOAuth
  • Links your own Telegram account to LMCP on this Mac. Shows a QR code (here and in a window on the Mac): on your phone open Telegram → Settings → Devices → Link Desktop Device and scan it. The Mac window also offers the phone-number login and asks for your two-step verification password if you have one. If that account is already connected, it says so. To link ANOTHER Telegram account, pass add_account: true (optionally with a label); `account` re-links an existing one (see telegram_list_accounts).
    ConnectorOAuth
  • A FEATURE FINDER, NOT A RECORD SEARCH. It searches Taokeh's own SCREENS, FEATURES and SETTINGS — never the books. Use it to tell the user WHERE in Taokeh to do something or change a setting: it returns the exact page(s) and what each one does, grounded in Taokeh's LIVE feature catalogue, so you never guess or invent navigation. ⛔ It does NOT look up documents, invoices, customers, products or any other RECORD, and it cannot tell you it failed to — a document number, a customer's DO/PO number, a person's name or an amount typed in here will still rank some page (the closest-worded screen), and that page will be a wrong answer wearing a right one's clothes. Records live elsewhere: search_documents (invoices, credit notes, quotes, delivery orders, bills, POs — and a customer's own Ref No), search_expenses (posted paid expenses), search_journal (ledger entries), resolve_customer / resolve_vendor / resolve_product (a named party or item), open_invoices (what one customer owes). Give a natural-language `query` about a CAPABILITY ("where do I turn on payment reminders", "how do I connect Shopee", "where's the SST setting") and it ranks the real features and hands back the top matches, each with the page's absolute deep-link URL(s), a one-line description of what the page does, an optional configHint (Taokeh keeps a feature's options on its OWN page, not in a global Settings menu), and an addOn flag (a paid add-on this company may not have). It GUIDES to the UI only — it changes nothing: no setting is ever toggled by the connector, that stays a human action in-app. If nothing matches it says so honestly — then tell the user to browse the left sidebar or contact support; never make up a path.
    ConnectorOAuth
  • Returns the macOS privacy (TCC) permissions Local MCP needs that are NOT granted yet, each with a one-click `open_url` that opens the exact System Settings → Privacy & Security pane. Read-only and passive (never prompts). Use it during setup or before a workflow to tell the user precisely which "Allow" clicks remain (Calendar, Contacts, Reminders, Automation for Mail/Messages/Notes/OmniFocus, Full Disk Access, Screen Recording, Accessibility) instead of failing mid-task. An installed app that is closed can't be checked and is listed under `unverified`. `all_granted: true` means nothing is left to do.
    ConnectorOAuth
  • Lists the Notion workspaces cached on this Mac. Start here for Notion — its output feeds notion_list_databases / notion_list_pages / notion_search. Does not return workspace members: the names and emails of third parties are not part of listing workspaces.
    ConnectorOAuth
  • Lists all mounted OneDrive directories on this Mac. Start here for OneDrive — the mount paths it returns are what the other onedrive_* tools (onedrive_list_files, onedrive_read_file, onedrive_search_files) need.
    ConnectorOAuth
  • Use this when someone asks which apps they track in AppSkyline, or an app's id is needed. Returns each app's id, name, default locale and its App Store, Mac App Store, Google Play and Microsoft Store ids, up to 100 apps. Not for finding other apps in a store.
    ConnectorNo auth
  • Use this when someone asks which apps they track in AppSkyline, or an app's id is needed. Returns each app's id, name, default locale and its App Store, Mac App Store, Google Play and Microsoft Store ids, up to 100 apps. Not for finding other apps in a store.
    ConnectorNo auth
  • Deletes a SAVED web-automation login profile: closes its window if open, erases its cookies and site data from this Mac, and removes it from web_session_list. Use it to clean up a profile that is no longer needed — web_session_close only closes the window and leaves the login (and its cookies) on disk. IRREVERSIBLE: the next web_login for that name starts from a signed-out browser. Requires confirm=true; without it you get a preview. Verify with web_session_list, which must no longer list the name.
    Connector
    Destructive
    OAuth
  • Cancel (delete) one reminder by its reminderId (ids come from list_reminders or create_reminder). The saved item itself is not touched. Reminders synced to Google Calendar cannot be cancelled here - the user manages those at mark-it.co or in Google Calendar.
    Connector
    Destructive
    No auth
  • Add, remove, or reinstate a person who receives an intake's invite and reminders, alongside or instead of the primary client. action="add" invites another address the same way also_notify does at define_intake time — its own message, its own bounce state; pass name to address it by name. action="remove" stops future reminders to that address. action="reinstate" is for a bounce that was wrong — the person did get the e-mail — and clears the bounce flag so reminders resume; if that address was the only one still being chased, the schedule is re-planned from now. Fails if the address is not on the intake, or — for reinstate — if it never bounced in the first place.
    Connector
    Destructive
    API key
  • Unlink Zalo from Local MCP (removes the saved session on this Mac). Your chats stay in Zalo; this only disconnects this Mac, and Zalo tools stop working until you run zalo_connect again. Write operation: first call (confirm=false) previews; confirm=true unlinks.
    ConnectorOAuth
  • Archive a scheme and upload the build to App Store Connect for TestFlight, with an App Store Connect API key kept on this Mac (keyId and issuerId; the issuer is remembered after the first upload). An uploaded build cannot be taken back and its build number is used up: confirm with the user first. buildNumber defaults to a UTC timestamp so every upload is new. Runs as a background job and returns its jobId; poll ios_build_status with it.
    Connector
    Destructive
    API key
  • Schedule several reminders at once — one thing spread over several dates, up to 20 per call. Each entry takes `fire_at_local` (the user's wall clock, ISO 8601, no zone) and `text`, delivered as written when it fires. All or nothing: 'limit_exceeded' says how many of the user's 20 reminder slots are free, so ask for at most that many or free some with cancel_reminder; 'invalid_payload' names the entry (reminders[i]) whose time is past, more than 180 days ahead, or whose text is empty. Applies instantly, no quota.
    ConnectorAPI key