@aernoud/remindersmcp

MCPcommunity

v0.2.0Aernoud DekkerMITUpdated 4mo agonpm GitHub

MCP server for macOS Reminders.app — list/reminder management via AppleScript

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

18Downloads/wk

5GitHub stars

1Forks

4mo agoLast update

Package

AuthorAernoud Dekker

LicenseMIT

Version0.2.0

Sourcenpm+mcp-registry

npm@aernoud/remindersmcp

GitHubaernouddekker/macos-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface22 tools · 3 privileged

Security scan✓ Cleanv0.2.0 · 1mo agoHow well does this scan work?

EvalsNone

IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

22 tools · 3 privileged

Statically extracted from the published packagev0.2.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

list-accountsList all accounts configured in macOS Reminders.app (e.g. iCloud, On My Mac)

List all accounts configured in macOS Reminders.app (e.g. iCloud, On My Mac)

No input schema was published for this tool.

list-listsList every reminder list, optionally scoped to a single account by name. Returns id, name, container account, color, and emblem for each list.

List every reminder list, optionally scoped to a single account by name. Returns id, name, container account, color, and emblem for each list.

No input schema was published for this tool.

get-listGet properties of a single list by name (id, account, color, emblem, open + completed reminder counts)

Get properties of a single list by name (id, account, color, emblem, open + completed reminder counts)

No input schema was published for this tool.

create-listCreate a new reminder list. If accountName is omitted, the list is created in the default account.

Create a new reminder list. If accountName is omitted, the list is created in the default account.

No input schema was published for this tool.

update-listRename a reminder list

Rename a reminder list

No input schema was published for this tool.

delete-listprivilegedDelete a reminder list by name. Reminders.app supports this directly via AppleScript (unlike Calendar.app).

Delete a reminder list by name. Reminders.app supports this directly via AppleScript (unlike Calendar.app).

No input schema was published for this tool.

show-listBring a list to the front in Reminders.app

Bring a list to the front in Reminders.app

No input schema was published for this tool.

list-remindersList reminders in a named list. Excludes completed by default.

List reminders in a named list. Excludes completed by default.

No input schema was published for this tool.

search-remindersSearch reminders by name substring. Optionally scope to one list (recommended — `whose` filters scan every reminder).

Search reminders by name substring. Optionally scope to one list (recommended — `whose` filters scan every reminder).

No input schema was published for this tool.

get-reminderGet full details of a reminder by id (searches all lists). Returns name, body, completed, completion/creation/modification dates, due date, allday due date, remind me date, priority, flagged.

Get full details of a reminder by id (searches all lists). Returns name, body, completed, completion/creation/modification dates, due date, allday due date, remind me date, priority, flagged.

No input schema was published for this tool.

today-remindersList reminders due today, scoped to one list or all lists.

List reminders due today, scoped to one list or all lists.

No input schema was published for this tool.

upcoming-remindersList reminders due in the next N days, scoped to one list or all lists.

List reminders due in the next N days, scoped to one list or all lists.

No input schema was published for this tool.

overdue-remindersList reminders whose due date is in the past and that are not yet completed.

List reminders whose due date is in the past and that are not yet completed.

No input schema was published for this tool.

create-reminderCreate a new reminder in a named list. Pass `dueDate` for a timed due date, OR `allDayDueDate` for a date-only due date — never both.

Create a new reminder in a named list. Pass `dueDate` for a timed due date, OR `allDayDueDate` for a date-only due date — never both.

No input schema was published for this tool.

update-reminderPatch fields on an existing reminder by id

Patch fields on an existing reminder by id

No input schema was published for this tool.

delete-reminderprivilegedDelete a reminder by id

Delete a reminder by id

No input schema was published for this tool.

complete-reminderMark a reminder as completed (Reminders.app stamps completion date automatically)

Mark a reminder as completed (Reminders.app stamps completion date automatically)

No input schema was published for this tool.

uncomplete-reminderMark a previously completed reminder as not completed

Mark a previously completed reminder as not completed

No input schema was published for this tool.

move-reminderprivilegedMove a reminder to a different list (uses Reminders.app's native `move` verb — id is preserved)

Move a reminder to a different list (uses Reminders.app's native `move` verb — id is preserved)

No input schema was published for this tool.

flag-reminderSet or clear the flagged state on a reminder

Set or clear the flagged state on a reminder

No input schema was published for this tool.

set-prioritySet the priority of a reminder. Maps to Reminders.app's integer enum: none=0, high=1, medium=5, low=9.

Set the priority of a reminder. Maps to Reminders.app's integer enum: none=0, high=1, medium=5, low=9.

No input schema was published for this tool.

show-reminderBring Reminders.app to the front and focus a specific reminder

Bring Reminders.app to the front and focus a specific reminder

No input schema was published for this tool.

22 of 22 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for macOS Reminders.app — list/reminder management via AppleScript

Keywords

mcpmcp-serverreminderstaskstodomacosapplescriptclaude

Alternatives

Comparing tool surfaces…

Tools exposed

22 tools · 3 privileged · observed 2026-09-01 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.6
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4
- cors2.8.6+1 not drawn1 dependency
  - object-assign4.1.1
- hono4.13.5
- jose6.2.10
- express5.2.1+27 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49
below the depth cap: 5

wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in notes & productivity

googleworkspace/cliGoogle Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Cha
@notionhq/notion-mcp-serverOfficial MCP server for Notion API
AgriciDaniel/claude-obsidianSelf-organizing AI second brain for Obsidian + Claude Code. Drop any source and Claude rea
makenotion/notion-mcp-serverOfficial Notion MCP Server
obsidian-second-brainOperate any Obsidian vault as a living, self-rewriting second brain (an evolution of Karpa
MarkusPfundstein/mcp-obsidianMCP server that interacts with Obsidian via the Obsidian rest API community plugin
taylorwilsdon/google_workspace_mcpControl Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive w
coddingtonbear/obsidian-local-rest-apiA secure REST API and Model Context Protocol (MCP) server for your vault.