Teamup Calendar MCP server

Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.

Connect Teamup Calendar50 free tool calls a month

What can I ask?

Turn on the Teamup Calendar connector, then ask in plain words. The AI picks the tools.

What you can do with Teamup Calendar in Claude and ChatGPT

For teams who share schedules, rooms and resources on a Teamup Calendar.

See what is on the calendar for a date range

The AI lists events in a date range, optionally for some sub-calendars, with recurring events expanded into each occurrence, so you see the week day by day.

Find events that mention a keyword

The AI searches events by keyword within a date range you choose and opens one event for its location, notes, signups and change history.

See who signed up for an event

The AI lists the people signed up for an event, with name and email, when signups are enabled on it.

List sub-calendars for people, rooms or resources

The AI lists the sub-calendars with their colors and active state, and opens one to show its overlap rule.

Add an event to the shared calendar

The AI creates an event on a sub-calendar with start and end time. You can undo the creation within one hour.

Changes data

Change or delete an event

The AI changes fields of an event, or of one occurrence of a recurring event, or deletes it. Deletions can be undone within one hour.

Changes data

How do I connect Teamup Calendar?

Before you connect

The login page asks for your Teamup API key and Calendar key or link.

The API key is free and personal: request your own at teamup.com/api-keys/request (Teamup uses it to know who runs an app, it gives no access to a calendar). The calendar key is the last part of a calendar link: open the calendar, go to Settings → Sharing, create a link with the permission you want the AI to have (read-only, add only, modify or admin), and paste the link or its key (it starts with ks). Both are used only to call the Teamup API on your behalf and are never shown to anyone.

Claude claude.ai · Desktop

  1. Open Customize → Connectors, then click + Add → Add custom connector.
  2. Enter the name Teamup Calendar and this URL, then click Add:
    https://teamup-calendar.usefulapi.io/mcp
  3. Claude opens the login page: enter your Teamup API key and Calendar key or link.
  4. In a chat, click + → Connectors and turn on Teamup Calendar.

Team and Enterprise: an Owner adds the connector for the organization first.

ChatGPT chatgpt.com

  1. Open Plugins, click +, then Add custom MCP server.
  2. Enter the name Teamup Calendar and this URL, choose OAuth as the authentication, confirm the warning and create it:
    https://teamup-calendar.usefulapi.io/mcp
  3. ChatGPT opens the login page: enter your Teamup API key and Calendar key or link.
  4. In Plugins, install Teamup Calendar, then choose it in a chat.

No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcp

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "teamup-calendar": {
      "url": "https://teamup-calendar.usefulapi.io/mcp"
    }
  }
}

VS Code

Add to VS Code or add this to .vscode/mcp.json:

{
  "servers": {
    "teamup-calendar": {
      "type": "http",
      "url": "https://teamup-calendar.usefulapi.io/mcp"
    }
  }
}

Codex

Run these commands. The second one opens the login page:

codex mcp add teamup-calendar --url https://teamup-calendar.usefulapi.io/mcp
codex mcp login teamup-calendar

Other clients

Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.

https://teamup-calendar.usefulapi.io/mcp

Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Teamup API key and Calendar key or link. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.

Guides

Pricing

PlanPriceLimit
Free$050 tool calls / month
Proper calendar$9/mo · $90/yr10,000 tool calls / month
Pro+per calendar$39/mo · $390/yr100,000 tool calls / month

Each paid plan covers this Teamup Calendar server only. Ask your AI to run teamup_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with teamup_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with teamup_upgrade before then undoes the cancel. Or write to support@usefulapi.io.

Tools 19

Show all 19 tools (the AI picks them for you)

Read only · 9

  • Get calendarteamup_get_calendar
    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.
  • List sub-calendarsteamup_list_subcalendars
    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 sub-calendarteamup_get_subcalendar
    One sub-calendar by id: name, color, overlap rule, active state and which links may use it.
  • List access keysteamup_list_access_keys
    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.
  • List eventsteamup_list_events
    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.
  • Search eventsteamup_search_events
    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 eventteamup_get_event
    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.
  • List changed eventsteamup_list_changed_events
    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.
  • List event signupsteamup_list_event_signups
    The people signed up for an event (name, email, id). Signups must be enabled on the event.

Changes data · 6

  • Create eventteamup_create_event
    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.
  • Update eventteamup_update_event
    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 the event and an undo_id for one hour (teamup_undo_event_action).
  • Delete eventteamup_delete_event
    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.
  • Undo event changeteamup_undo_event_action
    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.
  • Create sub-calendarteamup_create_subcalendar
    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.
  • Update sub-calendarteamup_update_subcalendar
    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.

Your usefulapi plan · 4

  • Usage status (free-tier meter)teamup_usage_status
    Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter.
  • Request a missing featureteamup_request_feature
    Tell usefulapi that the user needs something the Teamup Calendar tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter.
  • Upgrade to Pro or Pro+teamup_upgrade
    Get a paid plan for Teamup Calendar (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter.
  • Cancel the Pro subscriptionteamup_cancel_subscription
    Cancel the caller's Teamup Calendar Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run teamup_upgrade later to undo the cancel before the period ends. Does not count against the meter.

FAQ

What can I do with Teamup Calendar in Claude or ChatGPT?

See what is on the calendar for a date range. Find events that mention a keyword. See who signed up for an event. List sub-calendars for people, rooms or resources. Add an event to the shared calendar. Change or delete an event. See what you can do for the details.

Is this an official Teamup Calendar product?

No. usefulapi is an independent service. It is not affiliated with or endorsed by Teamup Calendar. The server calls the Teamup Calendar API with your own Teamup Calendar access, so it sees only the data that your account can see.

Can I connect Teamup Calendar to Claude or ChatGPT?

Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.

What do I need to connect?

The login page asks for your Teamup API key and Calendar key or link. See Before you connect for where to find them.

Do I put my Teamup Calendar key or an Authorization header in the client config?

No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Teamup API key and Calendar key or link. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.

How do you keep my Teamup Calendar credentials?

The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Teamup Calendar API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Teamup Calendar.

Can the AI change my Teamup Calendar data?

Yes, if you approve it. 6 of the 15 Teamup Calendar tools can create or change data. The other 9 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.

What does it cost?

The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Teamup Calendar server only. Cancel any time: your paid plan then runs to the end of the paid period. Run teamup_usage_status to see how many calls you used.

How do I subscribe or cancel?

Ask the AI to run teamup_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run teamup_cancel_subscription. Your paid plan continues to the end of the paid period.

What if a Teamup Calendar tool that I need is missing?

Tell the AI what you wanted to do. It can send the request with teamup_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.

Which AI clients can I use?

Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.

This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.

Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.

More Scheduling MCP servers

Acuity SchedulingAddEventAgendaProAladtecAppointeddAppointoArtesaAuvoBailaYaBedrijfsroosterBokadirektBookafyBookeobookingkitBookingmoodBuk.ngCheckfrontCorsizioCourtReserveCronofyeventOneGoTableHolidayPitchesHostawayHotelRunnerInzetroosterLeagueAppsMindbodyMoeGoMolzaitMomenceProgendaReclaim.aireenioReservioresOSRotageekSavvyCalSchedule itSetoraSlottableSmartplanTimeTapTrekkSoftWaitwhileWellknownWorkfeedYouCanBook.meZauiZenamu

All Scheduling servers →