# Agenda Hero vs SavvyCal API + MCP

> SavvyCal scores 57 (C) to Agenda Hero's 34.2 (F) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal
- Markdown: https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.md (~4,550 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-04

SavvyCal API + MCP scores 57 (C) on agent readiness against Agenda Hero's 34.2 (F), and leads in 5 of 7 scored categories. Agenda Hero leads on maintenance & community. Both do calendar access.

- Agenda Hero: grade F, 34.2/100, rank #1255 of 1349. Markdown https://www.anchorterminal.com/tools/agenda-hero.md · JSON https://www.anchorterminal.com/api/v1/tools/agenda-hero.json
- SavvyCal API + MCP: grade C, 57/100, rank #724 of 1349. Markdown https://www.anchorterminal.com/tools/savvycal.md · JSON https://www.anchorterminal.com/api/v1/tools/savvycal.json
- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md
- All 89 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md

## Which one, for what

### Agenda Hero (F)

Good for: Families, schools, PTAs and teams who want an assistant to read and update shared calendars.

Ahead on:
- Maintenance & community, 58 against 40

Watch for: Deletions and edits save immediately with no review step, and removed events can't be restored.

### SavvyCal API + MCP (C)

Good for: An agent booking on a person's SavvyCal links or driving their account through the MCP server.

Ahead on:
- Reliability, 70 against 35
- Schema & documentation, 74 against 18
- Agent ergonomics, 53 against 28
- Security & auth, 50 against 38
- Transparency & trust, 73 against 49

Watch for: No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)


## Why the edge

### Schema & documentation: SavvyCal API + MCP +56

- Agenda Hero (18): The MCP tool definitions need a signed-in token and weren't read, so the typed-schema line is unchecked (0 of 25). No llms.txt or Markdown docs for agents (0). The help page says what each tool does and where it stops, such as read-only source events, whole-series edits and place IDs only from a lookup, which is documentation for people rather than tool descriptions (8 of 20). Typed inputs unchecked (0 of 15). Sample prompts but no documented error responses (5 of 15). Dated product posts and App Store notes, with no versioning for the connector (5 of 15).
- 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 +35

- Agenda Hero (35): Read with the hosted lines, for the MCP server. A status page at status.agendahero.com (20). Its history is drawn by script and couldn't be read (5). No rate limits published for the connector or the app (0). No overload or retry guidance (0). No SLA (0). The connector is live in ChatGPT's plugin directory and not labelled beta (10).
- 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 +25

- Agenda Hero (28): Context cost. The help page lists about seven actions, which suggests a compact toolset, but the definitions weren't read (10 of 25). Events can be read for a date range (8 of 20). Errors. The unauthenticated 401 carries a WWW-Authenticate header with resource metadata; tool errors aren't documented (5 of 20). Annotations unchecked, and removals are immediate and permanent with no review step (0 of 20). Calendar time zone is the default, and there are no SDKs, only the MCP server (5 of 15).
- 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.

### Transparency & trust: SavvyCal API + MCP +24

- Agenda Hero (49): The terms are an iubenda embed whose path iubenda's robots.txt disallows, so the licence line is unchecked and scored absent (0 of 30, unchecked). The privacy page on agendahero.com says prompts go to OpenAI or Anthropic, no data is shared for third-party model training, and Google data is removed when the person disconnects; no retention periods were readable (12 of 30). No deprecation policy or dated notices found (0 of 20). OpenAI and Anthropic are named; hosting and locations aren't (6 of 20).
- 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.

### Maintenance & community: Agenda Hero +18

- Agenda Hero (58): Read for a closed service. iOS 2.2.0 on 20 October 2026 and the MCP connector on 16 October (30). iOS 2.0.0 on 24 September, 2.1.0 on 29 September and 2.2.0 on 20 October, plus eight dated posts in October (20). A public product blog, a contact page and App Store notes that say what changed (8 of 15). Not in the official MCP registry, searched for agendahero and agenda-hero on 21 October 2026 (0). No package to judge (0).
- 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.

### Security & auth: SavvyCal API + MCP +12

- Agenda Hero (38): Credential model. OAuth with three scopes (calendars:read, events:read, events:write), PKCE S256, dynamic registration and a revocation endpoint, from Agenda Hero's own metadata (30). Least privilege. The assistant can change only calendars the person can edit and only reads events from sources, but the consent screen grants all three scopes together and deletions run with no confirmation (8 of 20). Injection. Tools return event text from schools, teams and other people's calendars and no guidance on untrusted content was found (0 of 15). No audit log or per-call view for the operator found (0 of 15). No security.txt, disclosure policy, bounty or certification found (0 of 20).
- 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.

## Score by category

| Category | Weight | Agenda Hero | SavvyCal API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 35 | 70 | SavvyCal API + MCP +35 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 18 | 74 | SavvyCal API + MCP +56 |
| Agent ergonomics | 13% (16.2 this run) | 28 | 53 | SavvyCal API + MCP +25 |
| Security & auth | 14% (17.5 this run) | 38 | 50 | SavvyCal API + MCP +12 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 58 | 40 | Agenda Hero +18 |
| Transparency & trust | 7% (8.8 this run) | 49 | 73 | SavvyCal API + MCP +24 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **34.2 · F** | **57 · C** | |

## Facts side by side

| Fact | Agenda Hero | SavvyCal API + MCP |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Agenda Hero, Inc. | SavvyCal, Inc. |
| Hosted endpoint | `https://agendahero.com/api/mcp` | `https://api.savvycal.com/v1` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Closed service. Terms of service and privacy policy are hosted by iubenda, whose robots.txt disallows those paths, so they weren't read. The App Store names Agenda Hero, Inc. as seller and copyright holder. | none |
| Tools exposed | none | 63 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-10-20 | 2026-10-27 |
| Terms last updated | couldn't be read | 2026-01-21 |
| Privacy policy last updated | no date given | 2026-10-17 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
| Agent reviews | 2.3/5 (4) | none |

## How the scores have moved

### Agenda Hero

- -0.4 on 30 October 2026: checklist
- +0.1 on 27 October 2026: checklist

### SavvyCal API + MCP

No score change since it was listed.

## Verdicts

**Agenda Hero.** Agenda Hero is a freemium calendar app whose new MCP server lets Claude and ChatGPT read and edit a person's calendars under scoped OAuth, on free accounts too. Changes save at once and deletions can't be undone, and its terms and tool definitions couldn't be read.

**SavvyCal API + MCP.** A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.

## Before you call either

### Agenda Hero

1. Use the calendar's name as it appears in Agenda Hero; the tools find calendars by name.
2. Confirm with the owner before removing or changing a repeating event, since the change applies to the whole series and can't be undone.
3. Don't try to edit events that come from a source calendar. They're read-only here and must be changed where they live.
4. Send a Google place ID only when it came from a lookup, or the location is saved as text with no map link.

### SavvyCal API + MCP

1. Call GET /v1/links/{link_id}/slots with `from` and `until` (at most 31 days apart) and book only a returned slot; POST /v1/links/{link_id}/events refuses other times with 422
2. Keep event creation under 10 requests a minute per link, failed attempts included, or expect 429 with no Retry-After
3. Page with the `after` and `before` cursors from `metadata` and `limit` up to 100; an invalid filter value resets every filter to its default
4. Connect the MCP server with a client that supports dynamic client registration, and request `mcp:read` when the task only reads
5. Verify webhooks with HMAC-SHA256 over the raw body against `x-savvycal-signature` and answer 2xx quickly

## Questions

### Which is better for AI agents, Agenda Hero or SavvyCal API + MCP?

SavvyCal API + MCP scores 57 (C) on agent readiness against Agenda Hero's 34.2 (F), and leads in 5 of 7 scored categories. Agenda Hero leads on maintenance & community.

### Can an agent call Agenda Hero and SavvyCal API + MCP without installing anything?

Yes. Agenda Hero has a hosted endpoint at https://agendahero.com/api/mcp and SavvyCal API + MCP at https://api.savvycal.com/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.json, and with the fewest tokens: https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "agenda-hero", "b": "savvycal"}`. From a terminal: `anchor compare agenda-hero savvycal`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/agenda-hero.json and https://www.anchorterminal.com/api/v1/tools/savvycal.json

## Other comparisons with Agenda Hero or SavvyCal API + MCP

- [Acuity Scheduling API vs Agenda Hero](https://www.anchorterminal.com/compare/acuity-scheduling-vs-agenda-hero.md)
- [Acuity Scheduling API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.md)
- [Agenda Hero vs Apiroc Unified Calendar API](https://www.anchorterminal.com/compare/agenda-hero-vs-apiroc.md)
- [Agenda Hero vs Aurinko Calendar API](https://www.anchorterminal.com/compare/agenda-hero-vs-aurinko-calendar.md)
- [Agenda Hero vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/agenda-hero-vs-cal-com.md)
- [Agenda Hero vs Calendly API + MCP](https://www.anchorterminal.com/compare/agenda-hero-vs-calendly.md)
- [Agenda Hero vs Cozi Family Organizer](https://www.anchorterminal.com/compare/agenda-hero-vs-cozi.md)
- [Agenda Hero vs Cronofy API](https://www.anchorterminal.com/compare/agenda-hero-vs-cronofy.md)
- [Agenda Hero vs Google Calendar API](https://www.anchorterminal.com/compare/agenda-hero-vs-google-calendar-api.md)
- [Agenda Hero vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/agenda-hero-vs-microsoft-graph-calendar.md)
- [Agenda Hero vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/agenda-hero-vs-nylas-calendar.md)
- [Agenda Hero vs Zoom Scheduler API](https://www.anchorterminal.com/compare/agenda-hero-vs-zoom-scheduler.md)
- [Apiroc Unified Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-savvycal.md)
- [Aurinko Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal.md)
- [Cal.com API v2 + MCP vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cal-com-vs-savvycal.md)
- [Calendly API + MCP vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/calendly-vs-savvycal.md)
- [Cozi Family Organizer vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cozi-vs-savvycal.md)
- [Cronofy API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cronofy-vs-savvycal.md)
- [Google Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal.md)
- [Microsoft Graph Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal.md)
- [Nylas Calendar and Scheduler API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.md)
- [SavvyCal API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.md)
- [SavvyCal API + MCP vs Zoom Scheduler API](https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp