Skip to main content
Glama
mjucius

Cozi MCP Server

by mjucius

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COZI_EMAILYesYour Cozi Family Organizer account email address
COZI_PASSWORDYesYour Cozi Family Organizer account password

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
family_membersA

List family members. Use the id for appointment attendees. Returns: [{id, name, color?}].

get_listsA

Summarize all lists (no items). Optionally filter by 'shopping' or 'todo'. Returns: [{id, title, type, item_count, completed_count}].

get_list_itemsA

Items in one list. Excludes completed items by default. Returns: [{id, text, status, position?}].

create_listA

Create a list ('shopping' or 'todo'). Returns: {id, title, type}.

delete_listC

Delete a list. Returns true on success.

add_itemC

Add an item to a list. Returns: {id, text}.

update_itemA

Update an item's text and/or completion status. Pass text, completed, or both. When both are provided the text is updated first then status is updated as a separate request — these are NOT atomic. Returns: {id, text, status}.

remove_itemsC

Remove items from a list. Returns true on success.

get_calendarA

Appointments for one month. Returns: [{id, subject, day, all_day, start?, end?, end_day?, attendees?, location?, notes?}]. day is always the start day and end_day appears only on multi-day events; such an event is listed in every month it overlaps, so day may fall outside the month asked for.

create_appointmentA

Create a calendar appointment. start and end are ISO datetimes (e.g. '2026-06-15T10:00:00'). For all-day events (all_day=true) a bare date (e.g. '2026-06-15') is also accepted and end may equal start; a bare date on a timed event is an error. For a multi-day event put end on a later date — the span is preserved, and the result reports it as end_day. end before start is an error. For attendees, call family_members() first and pass those id values.

update_appointmentA

Partial-update an appointment. The Cozi PUT semantics replace ALL fields, so this tool first fetches the existing appointment from the (year, month) page and merges your changes — only fields you pass are altered. To switch a timed appointment to all-day pass all_day=true; to switch to timed pass new start/end. Passing end re-spans the event against its (possibly newly set) start day, so an end on a later date makes it multi-day and one on the start day collapses it back; passing start alone moves the event and keeps its length, and all_day=true preserves the span. A bare date (e.g. '2026-06-15') is accepted for start/end when the event is, or is being made, all-day; on a timed event it is an error.

delete_appointmentC

Delete an appointment. Returns true on success.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 12 tools

Disambiguation4/5

Tools are mostly distinct by resource (lists/items vs. appointments vs. family members), but update_item and add_item both target list items and could be confused when an agent wants to modify an item; remove_items vs. delete_list vs. delete_appointment are clear by resource. The calendar tools are well-differentiated.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (create_appointment, update_appointment, delete_appointment, get_calendar, get_lists, get_list_items, create_list, delete_list, add_item, remove_items). Minor inconsistency: add_item/remove_items use different verb forms (add vs. remove) and update_item is the only 'update' for items, but the pattern is still readable.

Tool Count5/5

12 tools is well-scoped for a family organizer server covering calendar, lists, and family members. Each tool maps to a distinct operation and none feel redundant.

Completeness4/5

The surface covers core lifecycle for lists (create/get/delete, add/update/remove items) and appointments (create/update/delete/get), plus family_members for attendees. Minor gaps: no way to update a list's title/type, no way to reorder items, and no search across calendar or lists, but agents can accomplish primary workflows.

Maintenance

ActivityMaintained
ResponsivenessWithin a week