Mjucius Cozi MCP server
{
"mcpServers": {
"cozi": {
"type": "http",
"url": "https://server.smithery.ai/@mjucius/cozi_mcp/mcp"
}
}
}{
"mcpServers": {
"cozi": {
"type": "http",
"url": "https://server.smithery.ai/@mjucius/cozi_mcp/mcp"
}
}
}{
"mcpServers": {
"cozi": {
"type": "http",
"url": "https://server.smithery.ai/@mjucius/cozi_mcp/mcp"
}
}
}{
"servers": {
"cozi": {
"type": "http",
"url": "https://server.smithery.ai/@mjucius/cozi_mcp/mcp"
}
}
}{
"mcpServers": {
"cozi": {
"type": "http",
"url": "https://server.smithery.ai/@mjucius/cozi_mcp/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.14.0
What it does
An MCP server that connects to Cozi Family Organizer, letting AI assistants read and update family calendars, lists, and related data. Each user runs their own instance against their own Cozi account, with credentials stored securely in the MCP client.
- View and create calendar appointments for family members in Cozi
- Read and update shopping lists, to-do lists, and other shared family lists
- Query family member information and calendar events to help with scheduling or planning tasks
Tools this server exposes
| Tool | Does |
|---|---|
| family_members | Get information about family members in the Cozi account. |
| get_lists | Retrieve all lists in the Cozi account. |
| get_list_items | Get items from a specific list in Cozi. |
| get_calendar | Retrieve calendar events from Cozi. |
| create_list_item | Add a new item to a Cozi list (write mode only). |
| update_list_item | Modify an existing list item in Cozi (write mode only). |
| delete_list_item | Remove an item from a Cozi list (write mode only). |
| create_calendar_event | Add a new event to the Cozi calendar (write mode only). |
| update_calendar_event | Modify an existing calendar event in Cozi (write mode only). |
| delete_calendar_event | Remove an event from the Cozi calendar (write mode only). |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.