Smart Calendars AI
v2.0.0Create and update subscription calendars from ChatGPT, Claude, or Codex.
Endpoint health
online- Last checked
- 11/20/2026, 6:18:28 AM
- Latency
- 369 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ai.smartcalendars%2Fsmart-calendars-ai
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ai.smartcalendars/smart-calendars-ai": {
"url": "https://api.smartcalendars.ai/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
7 shown · authentication unknown
Save a calendar revision
apply_feed_changes
Saves one revision to one existing calendar feed owned by the connected account for a user-approved schedule change. Accepts one fixed-schema change set with up to 250 event changes and/or a feed title or description change; all stored calendar changes commit together in one transaction, or none are saved. The schema declares every supported change: add creates an event; update changes selected fields or uses reset_fields to restore saved field baselines; delete marks an existing event canceled without permanently erasing it; restore reinstates that same event and may update selected fields; feed_patch changes only the calendar title or description. No dynamic operation discovery, fetched schemas, arbitrary commands or arbitrary endpoints are supported. dry_run=true validates and previews the proposed change set without saving calendar changes, advancing the revision or spending credits. The response contains the exact before/after changes and any billing quote. User approval of that exact preview is a prerequisite for saving with dry_run=false. Saving requires the returned preview_receipt and the identical feed_id, expected_revision, request_id, operations and feed_patch. The receipt binds that validated preview, not user consent. Changed proposals or expired previews require a new preview and approval; revision conflicts require current feed data and a new preview. Omitted events and fields remain unchanged. Cancellation assessment from a revised schedule requires the complete unfiltered event set; unrelated events and manual fields remain unchanged unless explicitly included in the approved changes. Uncertain event matches require user clarification. Updates address matched event IDs; a duplicate add is not an update. A recurring-series target is series_id with scope=occurrence, following or series; occurrence/following uses the original scheduled occurrence_date, including moved occurrences. reset_fields can include cancellation to restore source cancellation policy. Entire-series edits include history and all returned segments are part of the preview. Explicit null in set clears nullable fields; reset_fields restores saved baselines. expected_revision prevents overwriting concurrent changes. An uncertain save is retried with the identical request_id and payload, including the original preview_receipt, rather than a new operation. Included editing access has no credit charge or credit-consent prompt. A quoted one-credit editing window requires explicit user authorization of the deduction and resulting balance before confirm_credit_charge=true; that authorization may be added after preview. Preview approval or an automation default does not authorize credit spending. publication.status reports calendar-file preparation, not subscription access. distribution_ready reports subscription availability at the returned revision; availability may change afterward. Preview proposals are recoverable for up to one hour; expired drafts are removed automatically. Previewing temporarily stores only the exact proposed calendar fields, without writing calendar events or advancing their revision. Returned feed_id and request_id identify that exact proposal for recovery. Recovery accepts only feed_id, the original request_id, dry_run=true and recover_preview=true. Reconstructed changes, guessed identifiers and latest-preview selection are unsupported. Recovery returns the original unexpired preview and exact save_arguments without extending expiry, saving or spending credits. Saving a recovered preview requires fresh user approval of its exact changes and the returned save_arguments unchanged; confirm_credit_charge remains false without explicit authorization of the current quoted charge. Recovery is not consent. Recovery with saved=true reports an already completed save and requires no additional save. An unavailable or expired proposal requires current feed data, a new request_id, a new preview and user approval; a changed proposal is a new approval decision. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.
Connections
streamable-http
https://api.smartcalendars.ai/mcp