Skip to main content
Glama
Lingnik

icloud-reminders-mcp

by Lingnik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ICLOUD_USERNAMEYesApple ID email
ICLOUD_CALDAV_URLNoRoot URL; the library discovers your account's pNN shard from ithttps://caldav.icloud.com/
ICLOUD_APP_PASSWORDYesApp-specific password (xxxx-xxxx-xxxx-xxxx)
ICLOUD_REQUEST_TIMEOUTNoPer-request timeout (seconds)30
REMINDERS_ALLOW_DELETENoEnable the destructive delete_reminder toolfalse
REMINDERS_LIST_ALLOWLISTNoComma-separated list names the server may touch

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_listsA

List the iCloud reminder lists (VTODO collections) this server can see.

Returns each list's stable list_id, mutable list_name, URL, and item count.

list_remindersA

List reminders, earliest-due first (undated last). Defaults to incomplete only.

list accepts a list_id or display name (all lists if omitted). due_before / due_after are ISO-8601 dates or datetimes. Results are paginated via limit/offset; the response includes total and a truncated flag.

get_reminderA

Fetch a single reminder by its uid (optionally scoped to one list).

create_reminderB

Create a reminder (VTODO). list is required unless exactly one exists.

due is an ISO-8601 date (all-day) or datetime with timezone.

complete_reminderA

Mark a reminder complete (STATUS:COMPLETED + COMPLETED + PERCENT-COMPLETE:100).

update_reminderA

Patch mutable fields of a reminder, preserving everything else.

Omitted/null fields are left unchanged; pass an empty string ("") to clear notes, due, or url. Set completed true/false to complete/reopen. Uses ETag optimistic concurrency and retries on conflict.

delete_reminderA

Permanently delete a reminder. Gated: requires REMINDERS_ALLOW_DELETE=true on the server AND an explicit confirm=true argument.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a unique and clear purpose: complete, create, delete, get, list lists, list reminders, and update. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., complete_reminder, list_reminders), making them predictable and easy to understand.

Tool Count5/5

7 tools is well-scoped for a reminders server, covering all essential CRUD operations plus list management without unnecessary bloat.

Completeness5/5

The set provides full lifecycle management for reminders: create, read, update (including complete/reopen), delete, and list. It also includes list listing, which is necessary for context.

Maintenance

ActivityStale
ResponsivenessUnresponsive

Resources