A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Teamup Calendar 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.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http teamup-calendar-mcp-by-usefulapi https://teamup-calendar.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# teamup_get_calendar, teamup_list_subcalendars, teamup_get_subcalendar and 12 more
Teamup Calendar 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 teamup-calendar-mcp-by-usefulapi https://teamup-calendar.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
15 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.
The calendar this connection points at: title, timezone and date settings, custom event fields, sub-calendars, the permission of the calendar key in use and the plan's features. Call this first to learn the sub-calendar ids and the timezone. The calendar key itself is never returned. GET /{calendarKey}/configuration.
No parameter schema on file.
List the sub-calendars (the colored lanes that events belong to, such as people, rooms or resources). A key with admin permission also sees inactive ones. GET /{calendarKey}/subcalendars.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_inactive | boolean | no | Include inactive sub-calendars (default false). |
| name_contains | string | no | Only sub-calendars whose name matches this text. |
| limit | integer | no | Results per page, 1-200 (default 50). |
| offset | integer | no | Number of results to skip (default 0). Pass the previous reply's next_offset. |
One sub-calendar by id: name, color, overlap rule, active state and which links may use it. GET /{calendarKey}/subcalendars/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subcalendar_id | integer | yes | Sub-calendar id. |
List the calendar's access keys (sharing links and user accesses) with name, role, active state and per-sub-calendar permission. Needs a key with admin permission. The secret key values are never returned (they are secrets); use the id and name to tell links apart. GET /{calendarKey}/keys.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name_contains | string | no | Only keys whose link, user or group name matches this text. |
| type | string | no | Only this kind of access. |
| limit | integer | no | Results per page, 1-200 (default 50). |
| offset | integer | no | Number of results to skip (default 0). Pass the previous reply's next_offset. |
List the events in a date range, optionally only on some sub-calendars. Recurring events are expanded: every occurrence in the range is returned with its own id (series id + -rid- + start). Notes come as markdown. Times use the calendar's timezone unless tz is set. GET /{calendarKey}/events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | First day, yyyy-mm-dd (default: today). |
| end_date | string | no | Last day, inclusive, yyyy-mm-dd (default: start_date). Needs start_date; at most 366 days after it. |
| subcalendar_ids | array | no | Only events on these sub-calendars. |
| tz | string | no | Timezone for the times in the reply, e.g. Europe/Berlin. Default: the calendar's timezone. |
Search events by keyword (2-100 characters) within a date range (default: today only, so always pass the range you mean). Recurring events are expanded. Paged with limit and offset. GET /{calendarKey}/events?query=.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search text (Teamup's search syntax applies). |
| start_date | string | no | First day, yyyy-mm-dd (default: today). |
| end_date | string | no | Last day, inclusive, yyyy-mm-dd (default: start_date). Needs start_date; at most 366 days after it. |
| subcalendar_ids | array | no | Only events on these sub-calendars. |
| tz | string | no | Timezone for the times in the reply, e.g. Europe/Berlin. Default: the calendar's timezone. |
| limit | integer | no | Results per page, 1-200 (default 50). |
| offset | integer | no | Number of results to skip (default 0). Pass the previous reply's next_offset. |
One event by id: title, times, sub-calendars, location, who, notes (markdown), recurrence rule, custom fields, signups, comments, attachments (metadata), version, change history and reminders. Use the occurrence id (123-rid-<unix start>) for one occurrence of a recurring event. GET /{calendarKey}/events/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | Event id. |
Events created, changed or deleted since a Unix timestamp (at most 30 days back), for syncing. A recurring event comes back once, as its series, not as occurrences. Deleted events carry delete_dt. Pass the reply's timestamp as since_timestamp next time so nothing is missed. GET /{calendarKey}/events?modifiedSince=.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since_timestamp | integer | yes | Unix timestamp in seconds, at most 30 days in the past. |
| mode | string | no | synchronize (default): events created and deleted after the timestamp are left out. monitor: they are returned too. |
The people signed up for an event (name, email, id). Signups must be enabled on the event. GET /{calendarKey}/events/{id}/signups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | Event id. |
WRITE: create an event. Needs a calendar key with add or modify permission. Give at least subcalendar_ids, start and end. Not idempotent: a repeated call creates a second event. The reply holds the new event and an undo_id; teamup_undo_event_action removes the event again within one hour. POST /{calendarKey}/events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subcalendar_ids | array | yes | Sub-calendar ids the event belongs to (from teamup_list_subcalendars). |
| start | string | yes | Start, e.g. 2026-10-14T09:00:00 (calendar timezone) or with an offset such as +02:00. For an all-day event: yyyy-mm-dd. |
| end | string | yes | End, same format as start. Must not be before start. |
| all_day | boolean | no | True for an all-day event (default false). |
| title | string | no | Event title. |
| location | string | no | — |
| who | string | no | The "who" field. |
| notes | string | no | Notes, in markdown. |
| rrule | string | no | Recurrence rule (iCalendar RRULE, e.g. FREQ=WEEKLY;COUNT=10). Omit for a single event. |
| custom | object | no | Values of custom fields, keyed by field id (see teamup_get_calendar -> fields). |
| signup_enabled | boolean | no | Let people sign up (default false). |
| signup_limit | integer | no | Maximum signups; required by Teamup when signup_enabled is true. |
| signup_visibility | string | no | Who sees the signups: all_users or users_with_modify_permission. |
| comments_enabled | boolean | no | Allow comments (default false). |
| comments_visibility | string | no | Who sees the comments: all_users or users_with_modify_permission. |
WRITE: change fields of an event; fields you leave out keep their value (the event is read first and sent back with its version, so a concurrent edit is refused instead of overwritten; an event without a version is not changed). Needs modify permission. For a recurring event pass redit; use the occurrence id (123-rid-<unix start>) with single or future. Attachments are not touched. The reply holds
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | Event id (occurrence id for one occurrence of a recurring event). |
| redit | string | no | Which occurrences of a recurring event: single (only this one), future (this and all later ones) or all. |
| subcalendar_ids | array | no | Sub-calendar ids the event belongs to (from teamup_list_subcalendars). |
| start | string | no | New start (same formats as in teamup_create_event). |
| end | string | no | New end. |
| all_day | boolean | no | — |
| title | string | no | — |
| location | string | no | — |
| who | string | no | — |
| notes | string | no | New notes, in markdown. Replaces the old notes. |
| rrule | string | no | New recurrence rule; with redit all or future only. An empty string removes the recurrence (the series becomes a single event). |
| custom | object | no | Custom field values to set, keyed by field id; other custom fields keep their value. |
| signup_enabled | boolean | no | — |
| signup_limit | integer | no | — |
| signup_visibility | string | no | — |
| comments_enabled | boolean | no | — |
| comments_visibility | string | no | — |
WRITE, DESTRUCTIVE: delete an event, or for a recurring event the chosen occurrences. Needs modify permission. Not retried. The reply holds an undo_id; teamup_undo_event_action restores the event within one hour, after that the deletion is permanent. For one occurrence use the occurrence id (123-rid-<unix start>) and redit single (the default); redit all deletes the whole series. DELETE /{calendar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | Event id (occurrence id for one occurrence of a recurring event). |
| redit | string | no | For a recurring event: single (default), future or all. With all the whole series is deleted. |
| version | string | no | The event's version (from teamup_get_event). If set, the delete is refused when the event changed since. |
WRITE: undo a recent event creation, update or deletion with the undo_id from that call. Works for one hour only and is refused if someone else changed the event since. PUT /{calendarKey}/events/undo/{undo_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| undo_id | string | yes | The undo_id returned by create, update or delete. |
WRITE: create a sub-calendar. Needs a calendar key with admin permission, and the plan may limit how many exist. Not idempotent: a repeated call creates a second one. POST /{calendarKey}/subcalendars.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Sub-calendar name. |
| color | integer | no | Color number from Teamup's palette (default 17). |
| overlap | boolean | no | Allow overlapping events on it (default true). |
| active | boolean | no | Active (default true). |
WRITE: change a sub-calendar's name, color, overlap rule or active state; fields you leave out keep their value. Needs admin permission. Making a sub-calendar inactive hides it from users without admin rights. PATCH /{calendarKey}/subcalendars/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subcalendar_id | integer | yes | Sub-calendar id. |
| name | string | no | — |
| color | integer | no | — |
| overlap | boolean | no | — |
| active | boolean | no | — |
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 Teamup Calendar 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 Teamup Calendar 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.