member-berries-apple-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| briefingA | One-shot day briefing: today's calendar, due reminders, recent note titles, and conversation starters |
| calendarC | Search, create, and open calendar events in Apple Calendar (Member Berries) |
| notesB | Search, retrieve and create notes in Apple Notes (Member Berries). List/search return title + snippet by default; set includeBody=true or use get for full text. |
| remindersC | Search, create, complete, delete, and open reminders in Apple Reminders (Member Berries) |
| memberberriesC | Access Member Berries memories — conversation starters and recent activities. Built-in starters work without a custom host prompt. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Calendar, notes, and reminders map cleanly to distinct Apple apps, and briefing is a distinct one-shot aggregate. The only mild overlap is conversation starters/recent activity appearing in both briefing and memberberries, plus briefing surfacing note/calendar/reminder data without managing it; descriptions mostly resolve this.
All tool names are lowercase single nouns (briefing, calendar, notes, reminders, memberberries), which is a consistent convention even though it is noun-based rather than verb_noun. There is no mixed casing or inconsistent verb style.
Five tools is well within the 3-15 ideal range for a personal-assistant MCP. Each tool represents a distinct domain area, and multi-action capabilities are consolidated rather than split into many narrow tools.
Core create/search/open/complete operations exist, but calendar events and notes lack explicit update/delete operations, and reminders lacks update, leaving common lifecycle operations as dead ends. Briefing and memberberries are read-oriented, so coverage is functional but not complete.