Skip to main content
Glama
Sign In
Reminders MCP Server

Reminders MCP Server

by jagadeesh52423
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reminders MCP Server

An MCP (Model Context Protocol) server for interacting with macOS Reminders app via AppleScript.

Requirements

  • macOS

  • Node.js >= 18.0.0

  • Access to macOS Reminders app

Related MCP server: Apple Reminders MCP Server

Installation

npm install -g reminders-mcp

Or use directly with npx:

npx reminders-mcp

Usage

As an MCP Server

Add to your MCP client configuration:

{
  "mcpServers": {
    "reminders": {
      "command": "npx",
      "args": ["reminders-mcp"]
    }
  }
}

Or if installed globally:

{
  "mcpServers": {
    "reminders": {
      "command": "reminders-mcp"
    }
  }
}

Development

git clone https://github.com/jagadeesh52423/remainders-mcp.git
cd remainders-mcp
npm install
npm run dev        # Run with tsx
npm run inspector  # Run with MCP inspector

Available Tools

Lists

Tool

Description

list_reminder_lists

Get all reminder lists with names, IDs, and counts

create_reminder_list

Create a new reminder list

delete_reminder_list

Delete a list and all its reminders

rename_reminder_list

Rename an existing list

Reminders

Tool

Description

get_reminders

Get reminders with filtering (list, status, priority, date range, search)

get_reminder

Get a single reminder by ID

create_reminder

Create a new reminder

update_reminder

Update reminder properties

delete_reminder

Delete a reminder

complete_reminder

Mark reminder as completed/incomplete

Batch Operations

Tool

Description

batch_create_reminders

Create multiple reminders at once (max 100)

batch_update_reminders

Update multiple reminders at once (max 100)

batch_complete_reminders

Complete/uncomplete multiple reminders (max 100)

License

MIT

Available Tools

13 tools
batch_complete_remindersC

Mark multiple reminders as completed or incomplete at once.

Inputs: reminders (required), completed.

batch_create_remindersB

Create multiple reminders at once. More efficient than creating one at a time.

Inputs: reminders (required).

batch_update_remindersB

Update multiple reminders at once. More efficient than updating one at a time.

Inputs: reminders (required).

complete_reminderC

Mark a reminder as completed or incomplete.

Inputs: id (required), listName (required), completed.

create_reminderC

Create a new reminder in the specified list.

Inputs: name (required), listName (required), body, dueDate, +3 more.

create_reminder_listC

Create a new reminder list in macOS Reminders app.

Inputs: name (required).

delete_reminderA

Delete a reminder. This action cannot be undone.

Inputs: id (required), listName (required).

delete_reminder_listA

Delete a reminder list and all its reminders. This action cannot be undone.

Inputs: name (required).

get_reminderC

Get a single reminder by its ID.

Inputs: id (required), listName (required).

get_remindersB

Get reminders with optional filtering by list, completion status, priority, date range, or search text.

Inputs: listName, completed, priority, dueBefore, +3 more.

list_reminder_listsA

Get all reminder lists from macOS Reminders app. Returns list names, IDs, and reminder counts.

Inputs: no named parameters.

rename_reminder_listC

Rename an existing reminder list.

Inputs: currentName (required), newName (required).

update_reminderC

Update an existing reminder's properties. Only specified fields will be changed.

Inputs: id (required), listName (required), name, body, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    A3.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific resources (reminders, reminder lists) and actions (create, get, update, delete, complete, list, rename), with clear boundaries between individual and batch operations. An agent can easily distinguish between tools like 'create_reminder' and 'batch_create_reminders' based on their descriptions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout. The naming is predictable and readable, with clear conventions like 'create_reminder', 'get_reminders', 'update_reminder', 'delete_reminder_list', and 'batch_complete_reminders'. There are no deviations in style or structure.

    Tool Count5/5

    With 13 tools, the count is well-scoped for a reminders management server. Each tool earns its place by covering essential CRUD operations for both reminders and reminder lists, including individual and batch variants, without feeling excessive or thin. This aligns with typical server scopes of 3-15 tools.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for the reminders domain. It includes creation, retrieval, updating, deletion, and completion for reminders, plus list management operations (create, list, rename, delete). There are no obvious gaps, and agents can handle all core workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers