Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
Smart Calendars AI is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Create and update subscription calendars from ChatGPT, Claude, or Codex.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http smart-calendars-ai-mcp https://api.smartcalendars.ai/mcp
# 2 — ask your agent for something these tools do
# create_feed, list_feeds, get_feed and 4 more
Smart Calendars AI costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SMAll 1 server
smartcalendars1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http smart-calendars-ai-mcp https://api.smartcalendars.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Create and activate a subscription calendar from structured events. Extract the schedule yourself first. Free within feed allowances. No automatic monitoring is enrolled. Reuse request_id on retries. publication.status reports calendar-file preparation, not subscription access. Check distribution_ready for access at the reported revision; use get_feed_status for current availability. These tools m
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | Generate an opaque key for this save and reuse it unchanged for retries, to prevent duplicate changes. Not a user identifier, chat/session ID, or telemetry. Do not include personal data. |
| title | string | yes | — |
| description | string/null | no | A short description of this calendar, not the conversation or user profile. |
| activate | boolean | no | — |
| events | array | yes | — |
List the connected account’s feeds, management links and shared active-feed allowance. Only feeds marked counts_towards_active_limit use a slot; this page’s length is not the account’s usage. Deactivating a counted feed frees a slot but interrupts its subscription access, so ask the user first. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source monitoring,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| offset | integer | no | — |
Read events and the internal revision before editing. Request include_facets first and select returned values for known labels. Facet results describe the entire published active feed, independent of read filters or pagination. Nonempty filters also return filtered_subscription with canonical filters, matching_event_count and unmatched_filter_values. Use its URLs for that selection; top-level subs
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_id | string | yes | — |
| event_ids | array | no | — |
| external_keys | array | no | — |
| from | string | no | — |
| to | string | no | — |
| removal_state | no | — | |
| filters | object | no | Request include_facets first; use returned available_facets values for the desired known labels. Values are trimmed and case-insensitive; format accepts attendance-mode aliases. Values within a field |
| include_facets | boolean | no | Return available_facets ({value,label,count} entries), facet_coverage ({tagged_events,fallback_events,missing_events}), facets_truncated and facet_scope=published_active_events. Coverage distinguishes |
| limit | integer | no | — |
| offset | integer | no | — |
Read the feed’s last update, subscription availability (distribution_ready), editing access and configured monitoring status. This does not refresh or charge. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source monitoring, scheduled PDF checks or document refreshes. For requests solely for those unsupported actions, explain the limitation without reading fee
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_id | string | yes | — |
Save one revision to one existing calendar feed owned by the connected account. Submit 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 input schema declares every supported change: add creates an event; update changes selected fields or uses reset_fields to res
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_id | string | yes | Feed identity returned by a previous feed tool; used to address the selected calendar only. |
| expected_revision | integer | no | Last read feed revision; prevents overwriting concurrent edits. |
| request_id | string | yes | Generate an opaque key for this save and reuse it unchanged for retries, to prevent duplicate changes. Not a user identifier, chat/session ID, or telemetry. Do not include personal data. |
| operations | array | no | — |
| feed_patch | object | no | — |
| dry_run | boolean | no | — |
| recover_preview | boolean | no | Read the exact temporarily stored preview after losing its receipt or proposal. Requires dry_run=true and only feed_id and the original request_id; omit all other arguments. Does not save, extend expi |
| preview_receipt | string | no | Opaque receipt returned by a successful dry_run=true preview. Required when saving with dry_run=false. Return it unchanged with the same feed, revision, request_id and proposed changes. It is not user |
| confirm_credit_charge | boolean | no | — |
Deactivate a feed without deleting events or resetting editing windows. Confirm the user wants to interrupt subscription access. publication.status reports calendar-file preparation, not subscription access. Check distribution_ready for access at the reported revision; use get_feed_status for current availability. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_id | string | yes | Feed identity returned by a previous feed tool; used to address the selected calendar only. |
| expected_revision | integer | yes | Last read feed revision; prevents overwriting concurrent edits. |
| request_id | string | yes | Generate an opaque key for this save and reuse it unchanged for retries, to prevent duplicate changes. Not a user identifier, chat/session ID, or telemetry. Do not include personal data. |
Reactivate an existing feed free within account allowances. Does not reset the original editing window or modify events. publication.status reports calendar-file preparation, not subscription access. Check distribution_ready for access at the reported revision; use get_feed_status for current availability. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_id | string | yes | Feed identity returned by a previous feed tool; used to address the selected calendar only. |
| expected_revision | integer | yes | Last read feed revision; prevents overwriting concurrent edits. |
| request_id | string | yes | Generate an opaque key for this save and reuse it unchanged for retries, to prevent duplicate changes. Not a user identifier, chat/session ID, or telemetry. Do not include personal data. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Smart Calendars AI or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 2.0.0 · scanned 24 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestb8181f322b75ae889d458437c9cc9aac79b01408b72580959a92dc8fb7d038e5
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| create_feed | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_feeds | no tags | |
| get_feed | no tags | |
| get_feed_status | no tags | |
| apply_feed_changes | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| deactivate_feed | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| reactivate_feed | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb8181f322b75ae88
Scanned2026-10-24
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.0.
2.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Smart Calendars AI can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.