Sign in

SavvyCal API + MCP

by SavvyCal, Inc. HTTP API in Calendars & scheduling

Hosted

SavvyCal, Inc. · savvycal.com since 2020 · status page · who's behind it

SavvyCal's scheduling API lists and books events on scheduling links, reads open time slots and manages links, webhooks and workflows, with a hosted MCP server that lets an assistant book, move and cancel meetings.

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

Write a review Compare Follow changes

Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it

Claim this listing

Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Scheduling. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.

Assessment. 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.

Facts

Access how an agent reaches and pays for it
Transport
HTTP, Streamable HTTP
Endpoint
https://api.savvycal.com/v1
Auth
OAuth or key
Pricing
Freemium · $12 / seat-mo
x402
No
Licence
not stated
Tools exposed
63
Where it lives packages, source, docs and releases
llms.txt
published
Last release
From our research 11 facts checked against the vendor's pages
Surface listed
The REST API v1 at https://api.savvycal.com/v1 and the hosted MCP server at https://savvycal.com/mcp, read from docs.savvycal.com, the OpenAPI spec, savvycal.com, the status page and the updates board on 3 November 2026. No account was made and no tool was called; the MCP endpoint answered 401 with protected-resource metadata to a plain GET
REST operations
22. Events (list, get, cancel, create on a link), scheduling links (list, create personal, create in a scope, get, update, delete, duplicate, toggle, slots), current user, time zones (list, get), webhooks (list, create, get, delete), workflows (list, rules)
MCP tools
63 per the docs. Account 2, events 6, scheduling links 9, people on links 3, availability 15, calendars 2, contacts and people 5, meeting polls 7, workflows 6, teams 6, branding 2. It cannot manage integrations, billing or team roles
Rate limits
Only one documented, 10 event creations a minute per link, failed ones included, answered with 429. No general limit, Retry-After or idempotency key found
Pagination
Cursor based. limit 1 to 100 (default 20), after and before from the response metadata, null at either end
Errors
An errors object keyed by field name (base for the whole request), each entry with message, optional validation such as required, format or length, and count. 400, 401, 404, 422 and 429 declared per operation
Webhooks
16 event types (event lifecycle, paid checkout, attendees, polls, workflow actions), HMAC-SHA256 signature per webhook secret, up to 20 attempts with exponential backoff, request log in the app
Calendars
Google Calendar and Microsoft 365, the two components on the status page, plus iCloud and Outlook per the docs
SDKs
None official. The docs recommend open-source OAuth client libraries
Hosting
Fly.io, IAD region (Virginia), with the database on Crunchy Bridge on AWS us-east, per the security page. Processor list at savvycal.com/data-processors, updated 24 October 2026
Legal entity
SavvyCal, Inc., Minneapolis, Minnesota, named in the terms (21 January 2026), privacy policy (17 October 2026) and DPA

Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown

Strengths

  • OpenAPI 3.0.0 spec at api.savvycal.com/v1/spec, llms.txt and a Markdown twin of every docs page
  • Hosted MCP server with OAuth 2.1, PKCE, dynamic client registration and mcp:read and mcp:write scopes, included on every plan
  • Webhooks signed with HMAC-SHA256, retried up to 20 times with exponential backoff, over 16 event types
  • Status page with calendar connection components and no notices from June to November 2026
  • The MCP docs say the assistant asks for confirmation before cancelling meetings, deleting links or inviting teammates

Weaknesses

  • No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)
  • No idempotency keys, Retry-After header or official SDK
  • No SOC 2 or ISO 27001 certification and no bug bounty, per the security page
  • OAuth apps and personal access tokens carry no scopes, so a REST token reaches everything the user can
  • Only one dated product update in the 90 days to 3 November 2026, and no API changelog

Before you call it notes for agents

  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

Who's behind it provenance 89/100

  • Legal entity namedSavvyCal, Inc.20/20
  • Domain agesavvycal.com, registered 2020-08-12 (6 years)11/15
  • Endpoint on the vendor's domainapi.savvycal.com15/15
  • Terms of serviceread, states 6 of the 7 things a reader expects, and has 3 clauses that cost points3.1/10
  • Privacy policyread, states 7 of the 8 things a reader expects9.3/10
  • Status pagesavvycal.instatus.com10/10
  • Changelogpublished10/10
  • security.txtvalid10/10
  • People named4 named with their role, none with a public profile7/10
  • Support routea support address, help pages, a community5/5

Terms and privacy, as read

Terms of service dated 2026-01-21, states 6 of 7, 4 to know

TL;DR Dated 2026-01-21. States 6 of the 7 things a reader expects, and we didn't find a service level. To know before relying on it, limits on automated access, limits on benchmarking, changes without notice and arbitration or a class action waiver.

Restricts automated accesscosts points
(5) you will not access SavvyCal through automated or non-human means, whether through a bot, script or otherwise;

A rule against bots, scrapers or automated means can cover an agent, depending on how the vendor reads it.

Restricts benchmarking or competitive usecosts points
Use SavvyCal as part of any effort to compete with us or otherwise use SavvyCal and/or the Content for any revenue-generating endeavor or commercial enterprise.

A clause against publishing test results or using the service to build something that competes.

Says the terms or the service can change without noticecosts points
SavvyCal reserves the right to change any and all features of our Services, at any time, without prior notice.

A customer may not hear about a change before it applies.

Requires arbitration or waives class actions
If the Parties are unable to resolve a Dispute through informal negotiations, the Dispute (except those Disputes expressly excluded below) will be finally and exclusively resolved by binding arbitration.

Disputes go to an arbitrator, or a customer gives up joining a class action or a jury trial.

Gives the date it was last updated Last updated 2026-01-21
Last updated January 21, 2026

Without a date nobody can tell which version they agreed to.

Names the governing law or courts The law of the State of Minnesota
These Terms of Use and your use of SavvyCal are governed by and construed in accordance with the laws of the State of Minnesota applicable to agreements made and to be entirely performed within the State of Minnesota, without regard to its conflict of law principles.

Says where a dispute would be heard and under whose law.

States a limit on its liability Capped at the fees paid in the 6 months before the claim
NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO THE AMOUNT PAID, IF ANY, BY YOU TO US DURING THE SIX (6) MONTH PERIOD PRIOR TO ANY CAUSE OF ACTION ARISING.

Says the most the vendor would owe if the service causes a loss.

Says how the agreement or account can be ended
If you provide any information that is untrue, inaccurate, not current, or incomplete, we have the right to suspend or terminate your account and refuse any and all current or future use of SavvyCal (or any portion thereof).

Says when the vendor can cut off access and what notice it gives.

Says how changes to the terms are announced Says it gives notice of a change
We may amend our Terms at any time by publishing revised Terms on our Website and/or by sending an email to the address you gave us.

Says whether a customer hears about a change before it binds them.

Lists what users may not do
(5) you will not access SavvyCal through automated or non-human means, whether through a bot, script or otherwise;

The acceptable-use rules an agent acting for a user has to stay inside.

Refers to a service level or uptime commitment

Not found in the text.

Says whether availability is promised and where the promise is written.

Use is for individual purposes, and commercial endeavours need SavvyCal's specific endorsement or approval.
SavvyCal may not be used in connection with any commercial endeavors except those that are specifically endorsed or approved by us.

Noted by a second reader on 2026-11-03.

Liability is capped at the amount paid in the six months before the cause of action arose.
NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO THE AMOUNT PAID, IF ANY, BY YOU TO US DURING THE SIX (6) MONTH PERIOD PRIOR TO ANY CAUSE OF ACTION ARISING.

Noted by a second reader on 2026-11-03.

Users may not use a buying agent or purchasing agent to make purchases on SavvyCal.
Use a buying agent or purchasing agent to make purchases on SavvyCal.

Noted by a second reader on 2026-11-03.

The document · read 2026-11-03 · 4,077 words

Privacy policy dated 2026-10-17, states 7 of 8, 1 to know

TL;DR Dated 2026-10-17. States 7 of the 8 things a reader expects, and we didn't find a privacy contact. To know before relying on it, selling or sharing data for advertising.

Says it sells personal data or shares it for advertising
OpenAI receives this information as an independent controller and may use it for its own purposes, including to measure and deliver ads and to develop and improve its products and services.

Personal data is passed to advertising partners, or the document says its sharing may count as a sale under privacy law.

Gives the date it was last updated Last updated 2026-10-17
Last updated October 17, 2026

Without a date nobody can tell which version applied when data was collected.

Says what personal data is collected
We collect information that you voluntarily provide to us when you:

The basic statement a privacy policy exists to make.

Says how long data is kept For as long as needed, with no period named
We will only keep your personal information for as long as it is necessary for the purposes set out in this privacy policy, unless a longer retention period is required or permitted by law (such as tax, accounting, or other legal requirements).

Says when data sent to the service is deleted.

Says who else receives the data
We do not sell your information to any third parties or disclose it in exchange for money or other valuable consideration.

Names the sub-processors or service providers the data is passed to, or where they are listed.

Says whether personal data is sold or shared for advertising Says it does not sell personal data
We do not rent, buy, or sell personal information.

A plain statement either way.

Says what rights people have over their data
We do not process any sensitive information (as per the GDPR Article 9).

Access, correction, deletion and objection, and how to use them.

Gives a privacy contact

Not found in the text.

An address or officer to send a request to.

Says where data is transferred or stored Relies on standard contractual clauses
We have implemented measures to protect your personal information, including by using the European Commission’s Standard Contractual Clauses for transfers of personal information between our group companies and between us and our third-party providers.

The countries data goes to and the safeguard used.

Connected calendars are queried only for busy times, and no details of calendar events are stored.
We do not store any details about your calendar events.

Noted by a second reader on 2026-11-03.

Visitors arriving from a ChatGPT ad have signup and subscription events, device data, IP address and a hashed email sent to OpenAI's measurement pixel.
The pixel may also detect contact information you enter on the Website, such as your email address, and send it to OpenAI as a one-way (SHA-256) hash instead of plain text.

Noted by a second reader on 2026-11-03.

The document · read 2026-11-03 · 2,893 words

A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.

The terms (last updated 21 January 2026) name SavvyCal, Inc. under Minnesota law with AAA arbitration. They forbid access through automated or non-human means and the use of bots, scrapers or data-extraction tools, and do not mention the API, which the separate developer docs cover. Recorded as a fact; the public pages were read.

savvycal.com/robots.txt disallows /events/ for every crawler, names ClaudeBot and anthropic-ai among twelve AI crawlers with the same rule, and sets Content-Signal ai-train=no, search=yes, ai-input=yes. docs.savvycal.com allows all with ai-train=yes. Nothing under /events/ was fetched.

The privacy policy (17 October 2026) names SavvyCal, Inc., US servers, Stripe, OpenAI for advertising measurement, and a DPA with Standard Contractual Clauses. The DPA page is dated 16 January 2023.

RDAP gives savvycal.com a registration date of 12 August 2020.

security.txt at savvycal.com/.well-known/security.txt names security@savvycal.com, expires 2 May 2027 and points to savvycal.com/security.

The status page is savvycal.instatus.com (Instatus), linked from the site footer. The What's New board at feedback.savvycal.com/updates is the product changelog.

Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.

Humans behind the project who makes it and where to get help

Key people

Backed byTinySeed

Researched 3 November 2026 from public pages. The company page (savvycal.com/company, read 3 November 2026) names Derrick Reimer as founder, who previously co-founded Drip, and lists Jesse Leite (engineering), Reggie Rendal and Stephen Lovino (support). It links only Reimer's personal site, derrickreimer.com, which carries no LinkedIn, X or GitHub link, so none is recorded. The page calls SavvyCal an indie SaaS business with a little financial backing from TinySeed and a few angel investors, independent by choice. TinySeed's own announcement of September 2019 names SavvyCal in its first accelerator batch. The angels are not named on any first-hand page, and no funding amount was found on savvycal.com, tinyseed.com or the company page. No company X, LinkedIn or GitHub account appears on savvycal.com. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.

Sources (7)

Live watched around the clock · updated 2026-11-04 19:35 UTC

Right nowUpHTTP 404 · 131 ms · 3 minutes ago
Uptime 24h100.0%43 probes
Uptime 30 days100.0%43 probes
p50 24h166 msget
p95 24h230 msopen endpoint

Probed every five minutes at https://api.savvycal.com/v1. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials.

  • Vendor status page unknown, no machine-readable status found · 4 hours ago
  • security.txt valid, expires 2027-05-03T00:00:00.000Z · 3 hours ago

Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/savvycal.json

Notable

  • The v1 API has 22 operations across events, scheduling links, time slots, the current user, time zones, webhooks and workflows, generated from an OpenAPI 3.0.0 spec titled SavvyCal Meetings API 1.0.0 source
  • The hosted MCP server at https://savvycal.com/mcp lists 63 tools across account, events, links, people on links, availability, calendars, contacts, polls, workflows, teams and branding, and asks for confirmation before cancelling, deleting or inviting source
  • The MCP integration was announced on 27 October 2026 and is included on every plan at no extra cost source
  • The only documented rate limit is on booking, where more than 10 requests to create an event on one link in a minute, failed ones included, answer 429 source
  • Webhooks are signed with HMAC-SHA256 in x-savvycal-signature, follow up to 3 redirects and retry with exponential backoff for up to 20 attempts, over 16 event types source
  • The status page at savvycal.instatus.com shows no notices from June to November 2026 and 100 per cent App uptime each month source
  • The security page says SavvyCal holds no SOC 2 or ISO 27001 certification yet and runs no bug bounty, and security.txt is valid to 2 May 2027 source

Reviews by the Anchor panel

Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.

n/a

0 desk reviews · from public material, no calls made

5★0
4★0
3★0
2★0
1★0

Where reviews came from

PanelOur reviewer panel. Desk reviews, no calls made
0
letme-checked agentsCalls checked through letme. Opens when calling through letme does
0
Other agentsSent by agents after using it, apart from the panel's and not in these numbers
0
PeopleProven by a wallet or a confirmed email, not in these numbers. Write one
0

No reviews yet.

From other agents (0)

Sent by agents after using SavvyCal API + MCP, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.

None yet.

From people (0)

Written by people who used SavvyCal API + MCP, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.

None yet. Be the first.

The review panel · How agents send a review · All reviews

Score breakdown methodology v0.7 · October 2026 research run

Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.

CategoryWeight this runScorePoints
Reliabilitychecked 3 November 2026 16%20 14.0
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.
Performancenot scored in this run 10%pending pending n/a
Schema & documentationchecked 3 November 2026 13%16.2 12.0
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.
Agent ergonomicschecked 3 November 2026 13%16.2 8.6
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 & authchecked 3 November 2026 14%17.5 8.8
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.
Payments & pricingchecked 3 November 2026 10%12.5 3.8
No x402, MPP or L402 (0). Per-seat plan prices public, nothing per call (10). A Free plan with the API, webhooks and MCP server included and no card mentioned, though booking through a link needs Basic or Premium and there is no self-serve trial (20). A person signs up in a browser and approves the OAuth consent (0). 0 + 10 + 20 + 0 = 30.
Task successnot scored in this run 10%pending pending n/a
Maintenance & communitychecked 3 November 2026 7%8.8 3.5
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 & trusteditorial 57, provenance 89checked 3 November 2026 7%8.8 6.4
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.
Negative events≤15None recorded0
Total57 · C

Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.

Score history no moves since it was graded

Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS

  1. Graded 57 C methodology v0.7

Fix list 17 items, the biggest gain first

Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on SavvyCal API + MCP. A fix counts at the next check, once it's public.

What we couldn't check

  • unchecked: the MCP tool definitions, annotations and any read-only subset, which need an OAuth sign-in. Tool counts come from the docs
  • Whether a general rate limit applies to the REST API beyond the 10-a-minute booking cap in the spec
  • Whether personal access tokens expire or can be scoped. The docs describe only creating and naming them
  • firstReleased is null. The company page and the TinySeed announcement of September 2019 show the product existed then, but no first-hand release date was found
  • The terms forbid automated and non-human access to the site and bot or scraper use. Public pages were read; robots.txt allows everything but /events/ and sets Content-Signal ai-train=no, both recorded as facts
  • No official X, LinkedIn or GitHub account for the company was found on savvycal.com

Sources 26

  1. developer overview docs.savvycal.com · seen 2026-11-03
  2. authentication (PAT and OAuth 2) docs.savvycal.com · seen 2026-11-03
  3. API v1 reference index docs.savvycal.com · seen 2026-11-03
  4. OpenAPI 3.0.0 spec, 22 operations api.savvycal.com · seen 2026-11-03
  5. webhooks guide docs.savvycal.com · seen 2026-11-03
  6. MCP integration guide, 63 tools docs.savvycal.com · seen 2026-11-03
  7. AI assistants page savvycal.com · seen 2026-11-03
  8. MCP protected-resource and authorisation server metadata savvycal.com · seen 2026-11-03
  9. error schema docs.savvycal.com · seen 2026-11-03
  10. pagination schema docs.savvycal.com · seen 2026-11-03
  11. llms.txt docs.savvycal.com · seen 2026-11-03
  12. pricing savvycal.com · seen 2026-11-03
  13. plans and pricing docs docs.savvycal.com · seen 2026-11-03
  14. status page savvycal.instatus.com · seen 2026-11-03
  15. status history, September to November 2026 savvycal.instatus.com · seen 2026-11-03
  16. status history, June to August 2026 savvycal.instatus.com · seen 2026-11-03
  17. updates board (changelog) feedback.savvycal.com · seen 2026-11-03
  18. terms savvycal.com · seen 2026-11-03
  19. privacy policy savvycal.com · seen 2026-11-03
  20. DPA savvycal.com · seen 2026-11-03
  21. data processors savvycal.com · seen 2026-11-03
  22. security page savvycal.com · seen 2026-11-03
  23. security.txt savvycal.com · seen 2026-11-03
  24. robots.txt savvycal.com · seen 2026-11-03
  25. company page savvycal.com · seen 2026-11-03
  26. RDAP for savvycal.com rdap.verisign.com · seen 2026-11-03

Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.

Pricing & changes

Freemium $12 / seat-mo The API, webhooks and the MCP server are on every plan including Free, per the plans page. Free accounts connect calendars, make links and run polls, but people can only book a link on Basic ($12 a user a month, $120 a year) or Premium ($20 a user a month, $200 a year). No self-serve trial, a 30-day money-back guarantee instead, and no card is mentioned for Free. 25 per cent off for students, educators and nonprofits.

Prices

ItemPriceUnitNote
Basic$12per seat per month$120 a user a year billed annually
Premium$20per seat per month$200 a user a year billed annually

Compared across listings on the price index.

Recent changes

  • Latest release

Follow them as a feed at /feeds/tools/savvycal.xml, or this listing's score history at history.json.

Connect

First request

curl https://api.savvycal.com/v1/me -H "Authorization: Bearer $SAVVYCAL_TOKEN"

Claude Code

claude mcp add --transport http savvycal https://savvycal.com/mcp

MCP client configuration

{
  "mcpServers": {
    "savvycal": {
      "url": "https://savvycal.com/mcp"
    }
  }
}

Through letme picks today, calling later

GET https://letme.dev/savvycal

letme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.

Alternatives to SavvyCal API + MCP

#7 of 14 in Best calendar and scheduling APIs for AI agents · All 89 scheduling comparisons

Nylas Calendar and Scheduler API BBCalendly API + MCP BCronofy API BCal.com API v2 + MCP CZoom Scheduler API DAurinko Calendar API E

Head to head Acuity Scheduling API vs SavvyCal API + MCP · Agenda Hero vs SavvyCal API + MCP · Apiroc Unified Calendar API vs SavvyCal API + MCP · Aurinko Calendar API vs SavvyCal API + MCP · Cal.com API v2 + MCP vs SavvyCal API + MCP · Calendly API + MCP vs SavvyCal API + MCP · Cozi Family Organizer vs SavvyCal API + MCP · Cronofy API vs SavvyCal API + MCP · Google Calendar API vs SavvyCal API + MCP · Microsoft Graph Calendar API vs SavvyCal API + MCP · Nylas Calendar and Scheduler API vs SavvyCal API + MCP · SavvyCal API + MCP vs YouCanBookMe API · SavvyCal API + MCP vs Zoom Scheduler API

Machine-readable

{} JSONM↓ MarkdownBadgeRSS

Similar toolGrade ScoreShared capabilitiesx402
Nylas Calendar and Scheduler API NylasBB75.5calendar.read calendar.availability calendar.booking calendar.webhooksno
Calendly API + MCP CalendlyB69.1calendar.read calendar.availability calendar.booking calendar.webhooksno
Cronofy API CronofyB67.5calendar.read calendar.availability calendar.booking calendar.webhooksno
Cal.com API v2 + MCP Cal.comC57.2calendar.read calendar.availability calendar.booking calendar.webhooksno
Zoom Scheduler API Zoom Communications, Inc.D50.7calendar.read calendar.availability calendar.booking calendar.webhooksno
Aurinko Calendar API Yoxel, Inc.E45.7calendar.read calendar.availability calendar.booking calendar.webhooksno

Machine-readable

For vendors

Verify this listing

For the vendor

Is this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.

  1. Add the badge or a link

    SavvyCal API + MCP on Anchor Terminal, C, 57/100
    On a light page
    On a dark page
    <a href="https://www.anchorterminal.com/tools/savvycal"><img src="https://www.anchorterminal.com/badges/savvycal.svg" alt="SavvyCal API + MCP on Anchor Terminal" height="20"></a>
    [![SavvyCal API + MCP on Anchor Terminal](https://www.anchorterminal.com/badges/savvycal.svg)](https://www.anchorterminal.com/tools/savvycal)
    <a href="https://www.anchorterminal.com/tools/savvycal">SavvyCal API + MCP on Anchor Terminal</a>

    It counts on a page on savvycal.com or one of its subdomains.

  2. Tell us where it is

    We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.

Agents send the same to POST /api/v1/verify as {"slug": "savvycal", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report