# Cozi Family Organizer vs SavvyCal API + MCP (slim)

> SavvyCal scores 57 (C) to Cozi Family Organizer's 16.1 (F) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cozi-vs-savvycal.md (~4,000 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/cozi-vs-savvycal.json · canonical https://www.anchorterminal.com/compare/cozi-vs-savvycal
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

SavvyCal API + MCP scores 57 (C) on agent readiness against Cozi Family Organizer's 16.1 (F), and leads in 6 of 7 scored categories. Both do calendar access.

- Cozi Family Organizer: F 16.1, rank #1312 of 1349 · https://www.anchorterminal.com/tools/cozi.min.md
- SavvyCal API + MCP: C 57, rank #726 of 1349 · https://www.anchorterminal.com/tools/savvycal.min.md
- Cozi Family Organizer, good for Cozi is a shared family calendar, shopping-list and meal-planning app.
- SavvyCal API + MCP, good for An agent booking on a person's SavvyCal links or driving their account through the MCP server. Ahead on Reliability, 70 against 15; Schema & documentation, 74 against 15; Agent ergonomics, 53 against 10; Security & auth, 50 against 10; Maintenance & community, 40 against 0; Transparency & trust, 73 against 40. Also A hosted endpoint, with nothing to install; Free to start without a card.

| Category | Cozi Family Organizer | SavvyCal API + MCP |
| --- | --- | --- |
| Reliability (16%) | 15 | 70 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 15 | 74 |
| Agent ergonomics (13%) | 10 | 53 |
| Security & auth (14%) | 10 | 50 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 0 | 40 |
| Transparency & trust (7%) | 40 | 73 |

| Fact (where they differ) | Cozi Family Organizer | SavvyCal API + MCP |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Cozi, Inc. | SavvyCal, Inc. |
| Hosted endpoint | no (local only) | `https://api.savvycal.com/v1` |
| Transports |  | HTTP, Streamable HTTP |
| Licence | Proprietary service; see governing terms and the access limitations below. | none |
| Tools exposed | none | 63 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | none | 2026-10-27 |
| Terms last updated | 2026-10-13 | 2026-01-21 |
| Privacy policy last updated | 2026-06-11 | 2026-10-17 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | 2.3/5 (4) | none |

Why the edge:
- Schema & documentation, SavvyCal API + MCP +59: Cozi Family Organizer 15 (Public product and help material earns 15 points for explaining user workflows. No external-agent machine contract, input schemas or API error catalogue was verified. This score concerns integration documentation, not consumer usability.); SavvyCal API + MCP 74 (OpenAPI 3.0.0 at api.savvycal.com/v1/spec covers all 22 operations with 56 schemas; the MCP tools' schemas could not be read without signing in (23 of 25). llms.txt and a Markdown twin of every docs page (10). Only 8 of the 22 operations carry a description, and those state constraints (events must match an open slot, an invalid filter resets every filter) rather than when to choose another endpoint (10 of 20). Required flags on 14 of 43 parameters, 34 enum properties across the schemas, `limit` bounded 1 to 100, `until` at most 31 days after `from` (12 of 15). Example values on parameters and a documented error shape keyed by field, with 400, 401, 404, 422 and 429 declared per operation, but no full response examples (10 of 15). A /v1 path and a promise that changes are additive, with dated product updates on the feedback board but no API changelog (9 of 15). 23 + 10 + 10 + 12 + 10 + 9 = 74.)
- Reliability, SavvyCal API + MCP +55: Cozi Family Organizer 15 (No readable 90-day incident record established (5). The consumer or commercially available product is documented (10). No public external-agent rate limits, safe-retry contract or SLA were verified (0).); SavvyCal API + MCP 70 (Read with the hosted lines. Instatus page at savvycal.instatus.com with App, Microsoft 365, Google Calendar and Integrations components and a month-by-month history (20). No notices from June to November 2026 and 100 per cent App uptime each month, a clean record (30). The only limit with a number is in the OpenAPI spec, 10 event creations a minute per link, failed ones included; nothing covers the rest of the API (7 of 15). That 429 is declared with no Retry-After, backoff guidance or idempotency key, and webhooks are the only place retries are described (3 of 15). No SLA; the terms give the service as is (0). The v1 API is generally available and the MCP server, announced 27 October 2026, is not marked beta (10). 20 + 30 + 7 + 3 + 0 + 10 = 70.)
- Agent ergonomics, SavvyCal API + MCP +43: Cozi Family Organizer 10 (Documented user workflows and handoff controls earn 10 points. External-agent output controls, batching and safe write retries were not verified. Do not infer a callable API from the product's own AI functions.); SavvyCal API + MCP 53 (List responses are sized by `limit` (default 20, at most 100) with no field selection. The MCP server lists 63 tools with no documented toolset or read-only list, though a client can ask for the `mcp:read` scope alone (10 of 25). Cursor pagination with `after`, `before` and `limit`, and date and status filters on events (17 of 20). Errors name the field, the failed validation and a limit count, which an agent can act on, but a 429 carries no wait time (14 of 20). No idempotency key on booking or link creation, and the MCP annotations could not be read; the docs say the assistant confirms before cancelling, deleting or inviting (6 of 20). Creating an event needs five fields, and there is no official SDK in any language (6 of 15). 10 + 17 + 14 + 6 + 6 = 53.)
- Security & auth, SavvyCal API + MCP +40: Cozi Family Organizer 10 (Published account, privacy and user-control documentation earns 10 points. No external-agent credential scopes, per-call audit contract or complete least-privilege API were verified. Vendor security statements were not independently audited.); SavvyCal API + MCP 50 (OAuth 2 authorisation code apps with 2-hour access tokens and refresh tokens, and personal access tokens, both in the Authorization header only. The spec declares no scopes for either, and PAT expiry and revocation are not described. The MCP server uses OAuth 2.1 with PKCE S256, dynamic client registration, `mcp:read` and `mcp:write` scopes and a revocation endpoint (22 of 30). `mcp:read` gives a read-only MCP grant, and the vendor says the assistant asks before booking, cancelling, deleting or inviting. REST tokens have no read-only form (14 of 20). Invitee names, answers and metadata written by outsiders come back through events and webhooks with no injection guidance; the AI page says the assistant sees calendar conflicts but not event names (2 of 15). Webhook request logs and a Connected Apps list with revoke, but no per-call audit log for the operator (4 of 15). Valid security.txt to 2 May 2027, a security page and an SSDLC page, but no SOC 2 or ISO 27001 (the page says not yet) and no bug bounty (8 of 20). 22 + 14 + 2 + 4 + 8 = 50.)
- Maintenance & community, SavvyCal API + MCP +40: Cozi Family Organizer 0 (No dated service release series, support-response sample, official developer SDK or dependency health evidence established (0). An active website alone is not a release history.); SavvyCal API + MCP 40 (Read as a closed service. The newest dated change is the MCP integration of 27 October 2026 on the updates board (30). It is the only dated entry since 7 July, so fewer than three in 90 days (0 of 20). A public updates board, a feature request board and a support address with a stated 24-hour reply within US Central business hours (10 of 15). No official SDKs (0). No package to assess (0). 30 + 0 + 10 + 0 + 0 = 40.)
- Transparency & trust, SavvyCal API + MCP +33: Cozi Family Organizer 40 (Published product, commercial and privacy disclosures earn 35 points. Governing API terms, service-specific retention, deprecation commitments and infrastructure locations were not all established. Where only website terms were found, they are not presented as a partner API agreement.); SavvyCal API + MCP 73 (Closed service with terms that name SavvyCal, Inc. under Minnesota law and forbid automated access to the site, with the API left to the developer docs (15 of 30). The privacy policy (17 October 2026), DPA (16 January 2023) and processor list (24 October 2026) agree on US hosting, Stripe and return or destruction on termination, but no retention period is stated beyond account lifetime (22 of 30). The developer overview promises additive changes; there is no deprecation policy or dated notice, and the terms allow any feature to change without notice (5 of 20). A processor list with purposes, hosting on Fly.io in Virginia and Crunchy Bridge on AWS us-east, but no locations per processor (15 of 20). 15 + 22 + 5 + 15 = 57.)