[FEATURE] Apple Reminders integration: expose tags as a first-class field in reminder_create_v0 / reminder_update_v0

Resolved 💬 2 comments Opened May 17, 2026 by crux311 Closed May 20, 2026

Problem

The reminder_create_v0 and reminder_update_v0 tools in the Claude iOS app
expose title, notes, dueDate, priority, alarms, url, and recurrence
but no dedicated tags field. Apple Reminders treats tags as a first-class data
type with their own filter views and Smart List support. Per Apple's own docs:
"Add a tag to the tag field: Click the Add Tags field, then choose a tag"
(https://support.apple.com/guide/reminders/tag-reminders-remn45640f4f/mac).

The current omission breaks any tag-based workflow when reminders are created via
Claude.

Repro

  1. From the Claude iOS app, ask Claude to create a reminder with a tag (e.g.

"create a reminder 'git er done' tagged #ClaudeOS").

  1. Claude has no tags field to populate, so it falls back to writing #ClaudeOS

into the notes field.

  1. Open Reminders.app. The hashtag renders as plain text in the notes — not as a

real tag. The reminder does not appear under the #ClaudeOS tag filter or in any
Smart List filtered by that tag.

Putting the hashtag in the title field also fails — Apple's tag auto-detection
that fires when typing in the native UI does not fire on API writes.

Impact

Tags are how I organize reminders across multiple lists. Without tag support,
Claude-created reminders are second-class citizens: they live in the right list
but are invisible to tag-based queries and Smart Lists. I have to either manually
open each Claude-created reminder and add the tag in Apple's UI, or stop using
Claude for tag-aware reminder creation.

This also affects reads: if reminder_search_v0 doesn't filter by tag, agentic
workflows that query "all reminders tagged #ClaudeOS" can't be built end-to-end.

Prior art

Multiple third-party Apple Reminders MCP servers already expose tags as a
first-class field, including:

tag filter on search)

Claude Code)

The fact that community implementations consistently include tags suggests the
data model and user demand are both clear.

Suggested solution

Add a tags: string[] parameter to:

  • reminder_create_v0 (per-reminder, in reminders[] items)
  • reminder_update_v0 (per-update item)

And a tags filter parameter to reminder_search_v0.

EventKit on iOS exposes tags via EKReminder properties, so this should be a
straightforward passthrough on the app side.

Environment

  • Claude iOS app, current version (May 2026)
  • iOS 18.x, iPhone 17 Pro
  • Apple Reminders with tags configured

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗