Skedda MCP. Automate desk and room reservations with chat commands.

You're managing an office space, right? Skedda handles all the booking crap so you don't have to click through a dozen calendar grids just to secure a desk or a conference room. Your AI client uses this server to talk directly to your facility management system. It makes sure you never overbook anything and that you always know what's available.

To start, you can get a full rundown of everything in the building using list_spaces, which returns every single bookable area. You also gotta know where those areas are—list_venues gives you a list of all distinct physical locations managed by Skedda. If you need to filter those spaces by type, list_space_categories pulls up an organized list of everything from 'Hot Desks' to 'Boardrooms'.

And if you gotta find a specific person for the reservation, use list_users; it gives you a directory of every employee or member associated with your account.

When you need to know what's open, you can check availability in two ways. First, list_bookings lets you pull up every single booking record in the system; you can even filter that list by specific date ranges if you want to see exactly when things are booked. If you're only looking at one spot—say, a specific boardroom for next Tuesday—you use get_booking_details to pull all the precise information about just that existing reservation.

Knowing who's there and when is key.

Changing or making reservations is where it gets smooth. You don't have to manually input everything; your agent handles it using plain language commands. If you need a new spot booked, create_booking takes the necessary space ID, user ID, and start/end time to book that resource instantly. But if plans change, no sweat.

Use update_booking to adjust details on an existing booking—you can move the entire slot or switch up who's assigned without having to delete and re-create it.

And listen, sometimes you gotta kill a reservation entirely. If a meeting gets canceled last minute, delete_booking permanently removes that entry from the system; remember, this action can't be undone.

Basically, your agent handles the whole lifecycle: listing all spaces and venues with list_spaces, getting a user directory with list_users, checking what’s already taken using filtered views via list_bookings or direct checks with get_booking_details, and then performing any action—creating, updating, or deleting bookings—using the dedicated functions.