A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
AddEvent MCP by usefulapi 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.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read AddEvent calendars, events, RSVPs and subscribers; create and update calendars and events.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http addevent-mcp-by-usefulapi https://addevent.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# addevent_list_calendars, addevent_get_calendar, addevent_create_calendar and 15 more
AddEvent MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
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 addevent-mcp-by-usefulapi https://addevent.usefulapi.io/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
18 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.
List the account's calendars (newest first by default) with id, title, timezone, whether it is the default calendar, landing-page links and counts of events and subscribers. GET /calendars.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_ids | array | no | Only these calendar ids. |
| sort_by | string | no | Sort field (default created). |
| sort_order | string | no | Sort direction. Needs sort_by. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-20 (default 10). |
One calendar by id: title, timezone, week start, template ids, subscriber and event counts, links, custom data. GET /calendars/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_id | yes | Calendar id (see addevent_list_calendars). |
WRITE: creates a new calendar in the AddEvent account (a new, empty calendar; nothing existing is changed and nobody is notified). Needs a title. POST /calendars.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Calendar title (single line). |
| timezone | string | no | Default timezone for events on this calendar (IANA name). |
| weekday_begin | string | no | First day of the week. |
| description | string | no | Shown on the calendar landing page. |
| internal_name | string | no | Internal name, never shown publicly. |
| calendar_color | integer | no | Color 1-20 from the palette. |
| landing_page_template_id | string | no | Calendar landing page template id, or 'default' (see addevent_list_calendar_templates). |
| embeddable_calendar_template_id | string | no | Embeddable calendar template id, or 'default'. |
| custom_data | object | no | Arbitrary key-value pairs to store on the object (snake_case keys), e.g. an external id. |
WRITE: changes fields of an existing calendar (only the fields you pass; the rest stay). Title, description and timezone changes show on its landing page and can reach people who subscribe to the calendar feed. Not reversible by this server (no previous values are kept), so read the calendar first. PATCH /calendars/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_id | yes | Calendar id to change. | |
| title | string | no | New title (single line). |
| timezone | string | no | IANA timezone such as America/Los_Angeles, or 'floating' (same local time for everyone). See addevent_list_timezones. |
| weekday_begin | string | no | — |
| description | string | no | — |
| internal_name | string | no | Internal name, never shown publicly. |
| calendar_color | integer | no | Color 1-20 from the palette. |
| landing_page_template_id | string | no | — |
| embeddable_calendar_template_id | string | no | — |
| custom_data | object | no | Key-value pairs to store on the calendar (snake_case keys). |
Search the account's events (newest created first; by start time when a date filter is used): title, start/end, timezone, location, RSVP settings and stats, landing-page links. Filter by calendar, event ids, text, date window or a custom_data pair. GET /events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_ids | array | no | Only events on these calendar ids. |
| event_ids | array | no | Only these event ids. |
| starts_before | string | no | Only events that start before this date-time (datetime_max; naive comparison, timezones ignored). |
| ends_after | string | no | Only events that end after this date-time (datetime_min; naive comparison, timezones ignored). |
| search | string | no | Case-insensitive text in title, internal name, description or location. |
| custom_data_key | string | no | Custom data key (needs custom_data_value). |
| custom_data_value | string | no | Custom data value (needs custom_data_key). |
| sort_by | string | no | Sort field. |
| sort_order | string | no | Sort direction. Needs sort_by. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-20 (default 10). |
One event by id (evt-...): all fields incl. description, organizer, reminder, recurring rule, RSVP settings and stats, custom data and share links. GET /events/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | Event id, like evt-0f571af553d8437eb6a9ce22384fdcba (see addevent_list_events). |
WRITE: creates a new event on a calendar (the account's default calendar if calendar_id is omitted). Creates a public event landing page and share links; it does not e-mail anyone, though people subscribed to that calendar's feed will see the event on their next sync. Needs title and datetime_start. POST /events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Event title (single line). |
| datetime_start | string | yes | Start date-time: YYYY-MM-DD, YYYY-MM-DD hh:mm or YYYY-MM-DD hh:mm:ss. |
| calendar_id | no | Calendar to add the event to (see addevent_list_calendars); default calendar if omitted. | |
| datetime_end | string | no | End date-time (default: start + 1 hour). Same formats as the start. |
| all_day_event | boolean | no | All-day event: only the dates are used. |
| timezone | string | no | IANA timezone for the start/end (default: the calendar's timezone), or 'floating'. |
| recurring_rule | string | no | iCalendar recurrence rule such as FREQ=WEEKLY;COUNT=10. The start must match the rule. Omit for a one-off event; on update an empty string makes the event stop repeating. |
| description | string | no | Plain text or simple HTML (keep under ~500 characters for cross-browser links). |
| internal_name | string | no | Internal name, never shown publicly. |
| location | string | no | Address or URL (meeting link). Use either location or location_id, not both. |
| location_id | integer | no | Id of a saved location (0 = none). Not together with location. |
| organizer_name | string | no | Organizer name (needs organizer_email). |
| organizer_email | string | no | Organizer e-mail (needs organizer_name). |
| reminder | integer | no | Minutes before the start for a calendar-app reminder (0-10800). |
| color | integer | no | Color 1-20 from the palette. |
| free_busy | string | no | How the event shows in an attendee's calendar. |
| landing_page_template_id | string | no | Event landing page template id or 'default' (see addevent_list_event_templates). |
| rsvp_enabled | boolean | no | Require an RSVP before the event can be added to a calendar. |
| rsvp_form_id | string | no | RSVP form id or 'default' (see addevent_list_rsvp_forms). |
| custom_data | object | no | Arbitrary key-value pairs to store on the object (snake_case keys), e.g. an external id. |
WRITE: changes fields of an existing event (only the fields you pass; the rest stay). The change goes live on its landing page and share links, and people who subscribed to the calendar or added the event with a live link are updated on their next calendar sync, so a time or location change can notify real people. No previous values are kept: read the event first. PATCH /events/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | Event id (evt-...) to change. | |
| title | string | no | New title (single line). |
| datetime_start | string | no | New start: YYYY-MM-DD, YYYY-MM-DD hh:mm or YYYY-MM-DD hh:mm:ss. |
| calendar_id | no | Move the event to this calendar id. | |
| datetime_end | string | no | End date-time (default: start + 1 hour). Same formats as the start. |
| all_day_event | boolean | no | All-day event: only the dates are used. |
| timezone | string | no | IANA timezone for the start/end (default: the calendar's timezone), or 'floating'. |
| recurring_rule | string | no | iCalendar recurrence rule such as FREQ=WEEKLY;COUNT=10. The start must match the rule. Omit for a one-off event; on update an empty string makes the event stop repeating. |
| description | string | no | Plain text or simple HTML (keep under ~500 characters for cross-browser links). |
| internal_name | string | no | Internal name, never shown publicly. |
| location | string | no | Address or URL (meeting link). Use either location or location_id, not both. |
| location_id | integer | no | Id of a saved location (0 = none). Not together with location. |
| organizer_name | string | no | Organizer name (needs organizer_email). |
| organizer_email | string | no | Organizer e-mail (needs organizer_name). |
| reminder | integer | no | Minutes before the start for a calendar-app reminder (0-10800). |
| color | integer | no | Color 1-20 from the palette. |
| free_busy | string | no | How the event shows in an attendee's calendar. |
| landing_page_template_id | string | no | Event landing page template id or 'default' (see addevent_list_event_templates). |
| rsvp_enabled | boolean | no | Require an RSVP before the event can be added to a calendar. |
| rsvp_form_id | string | no | RSVP form id or 'default' (see addevent_list_rsvp_forms). |
List RSVP attendees (personal data: e-mail addresses and the answers they gave on the RSVP form). Filter by calendar, event or response (going/maybe/not-going). Paged, 20 at most per page: read only what the task needs. IP address and coordinates are removed from the reply. GET /rsvps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_ids | array | no | Only attendees of these event ids. |
| calendar_ids | array | no | Only attendees of events on these calendar ids. |
| attending | string | no | Only attendees with this response. |
| sort_by | string | no | — |
| sort_order | string | no | Sort direction. Needs sort_by. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-20 (default 10). |
One RSVP attendee by id (personal data: e-mail and form answers; IP address and coordinates removed). GET /rsvps/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attendee_id | yes | RSVP attendee id (see addevent_list_rsvp_attendees). |
WRITE: adds ONE RSVP attendee (one e-mail address, personal data) to an event. This server never asks AddEvent to send the confirmation or organizer notification e-mails, but the event's own reminder and follow-up e-mails (if the event has them) will later go to this address, so only add someone who really RSVP'd. The e-mail must be unique per event. POST /events/{id}/rsvps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | Event id (evt-...) to RSVP to. | |
| string | yes | Attendee e-mail address (unique per event). | |
| attending | string | no | The attendee's response. |
| rsvp_form_data | object | no | Answers to the event's RSVP form as field-name -> value. The default form needs {"name": "..."}. |
WRITE: changes ONE RSVP attendee (email, response or form answers; only the fields you pass). The event's reminder and update e-mails go to the e-mail address stored here, so changing it redirects those e-mails to that person. This server never triggers the confirmation or organizer notification e-mails. PATCH /rsvps/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attendee_id | yes | RSVP attendee id. | |
| string | no | New e-mail address. | |
| attending | string | no | — |
| rsvp_form_data | object | no | Answers to the event's RSVP form as field-name -> value. The default form needs {"name": "..."}. |
List people subscribed to the account's calendars (personal data: the form answers they gave, such as name and e-mail; calendar app type, sync status). Paged, 20 at most per page. IP address and coordinates are removed. GET /subscribers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_ids | array | no | Only subscribers of these calendar ids. |
| status | string | no | active = synced in the last 30 days; inactive = not; blocked = blocked by the owner. AddEvent returns only active ones when omitted, so call once per status. |
| sort_by | string | no | — |
| sort_order | string | no | Sort direction. Needs sort_by. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-20 (default 10). |
One calendar subscriber by id (personal data; IP address and coordinates removed). GET /subscribers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subscriber_id | yes | Subscriber id (see addevent_list_calendar_subscribers). |
The account's RSVP forms (id, name), newest first. Use the id as rsvp_form_id on an event. GET /events/rsvp-forms.
No parameter schema on file.
The account's event landing page templates (id, name), newest first. Use the id as landing_page_template_id on an event. GET /events/templates.
No parameter schema on file.
The account's calendar landing page templates or embeddable calendar templates (id, name), newest first. Use the id as landing_page_template_id / embeddable_calendar_template_id on a calendar. GET /calendars/templates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | calendar-landing (default) or calendar-embed (embeddable calendars). |
Timezone names AddEvent supports (use them as the timezone of events and calendars), with current UTC offset. Optional text filter on the name. GET /timezones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Case-insensitive part of the name, e.g. 'Prague' or 'America/'. |
| limit | integer | no | Most entries to return (default 100). |
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 AddEvent MCP by usefulapi 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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 1.0.0.
1.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 AddEvent MCP by usefulapi 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.