A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Youcanbookme 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.
What it does
Manage YouCanBook.me bookings, booking pages, appointment types, team members and locations.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http youcanbookme-mcp https://youcanbookme.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# list_bookings, get_booking, list_profiles and 15 more
Youcanbookme costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 youcanbookme-mcp https://youcanbookme.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
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 bookings (appointments) on the YouCanBookMe account. YCBM API: GET /v1/bookings. Filter by profileId (booking page), an after/before time window, cancelled status, and a free-text searchText; select fields with fields. Paginated via page (0-based) + maxResults. Returns a JSON array of bookings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | no | Restrict to bookings on this profile (booking page) id. |
| after | string | no | Only bookings starting AFTER this time (ISO 8601, e.g. 2026-07-01T00:00:00Z). |
| before | string | no | Only bookings starting BEFORE this time (ISO 8601). |
| cancelled | boolean | no | Filter by cancelled status: true = only cancelled, false = only active. Omit for all. |
| searchText | string | no | Free-text search across booking fields (e.g. attendee name/email). |
| fields | string | no | Comma-separated field paths to return (e.g. "id,title,startsAt"). Supports dotted paths for nested objects. Omit to get the default field set. |
| page | integer | no | Pagination page number, 0-based (offset-based paging). Use with maxResults. |
| maxResults | integer | no | Maximum records per page (page size). Defaults to the API's own default when omitted. |
| params | object | no | Additional documented query-string filters to send verbatim (merged with the typed params above). |
Fetch a single booking (appointment) by id. YCBM API: GET /v1/bookings/{bookingId}. Use fields to select which fields to return. Returns the booking object.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bookingId | string | yes | The booking id. |
| fields | string | no | Comma-separated field paths to return (e.g. "id,title,startsAt"). Supports dotted paths for nested objects. Omit to get the default field set. |
List all profiles (booking pages) on the account. YCBM API: GET /v1/profiles. A profile is a bookable page with its own subdomain, appointment types, team members, and locations. Use fields to select fields (e.g. "id,title,subdomain"). Paginated via page (0-based) + maxResults. Returns a JSON array of profiles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | string | no | Comma-separated field paths to return (e.g. "id,title,startsAt"). Supports dotted paths for nested objects. Omit to get the default field set. |
| page | integer | no | Pagination page number, 0-based (offset-based paging). Use with maxResults. |
| maxResults | integer | no | Maximum records per page (page size). Defaults to the API's own default when omitted. |
| params | object | no | Additional documented query-string filters to send verbatim (merged with the typed params above). |
Fetch a single profile (booking page) by id. YCBM API: GET /v1/profiles/{profileId}. Use fields to select fields, including nested sub-resources (appointmentTypes, teamMembers, locations). Returns the profile object.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id. |
| fields | string | no | Comma-separated field paths to return (e.g. "id,title,startsAt"). Supports dotted paths for nested objects. Omit to get the default field set. |
List the team members configured on a profile (booking page). YCBM API: GET /v1/profiles/{profileId} with a teamMembers field selection. Returns the profile's teamMembers block (each member has id, name, email, description, pic, calendarId).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id. |
List the appointment types configured on a profile (booking page). YCBM API: GET /v1/profiles/{profileId} with an appointmentTypes field selection. Returns the profile's appointmentTypes block (each with id, name, description, slotLength, price).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id. |
List the locations configured on a profile (booking page). YCBM API: GET /v1/profiles/{profileId} with a locations field selection. Returns the profile's locations block (each with id, kind, value, notes, strategy).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id. |
List the accounts/calendars available to your account — used to find the calendarId for a team member. YCBM API: GET /v1/{accountId}/availableAccounts (accountId is taken from your configured credentials). Returns a JSON array.
No parameter schema on file.
Power-user escape hatch: GET any YCBM API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the origin, starting with a slash, INCLUDING any query string, e.g. "/v1/bookings?maxResults=5" or "/v1/profiles". Returns the parsed JSON.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Full API path after the origin, starting with "/", e.g. "/v1/bookings?maxResults=5". |
MUTATES YouCanBookMe data: creates a booking (appointment) on a profile. YCBM API: POST /v1/bookings (JSON). Required: profileId, startsAt, endsAt (ISO 8601 times). Optional: title, timeZone, locale, units. Complex fields like answers (form-field answers) and linkFields should be passed via the fields passthrough. Returns the created booking.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id to book on (required). |
| startsAt | string | yes | Booking start time, ISO 8601 (required). |
| endsAt | string | yes | Booking end time, ISO 8601 (required). |
| title | string | no | Booking title. |
| timeZone | string | no | IANA time zone for the booking (e.g. Europe/London). |
| locale | string | no | Locale for the booking (e.g. en-GB). |
| units | integer | no | Number of slot units to book. |
| fields | object | no | Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above. |
MUTATES YouCanBookMe data: updates an existing booking (reschedule, rename, mark cancelled/no-show). YCBM API: PATCH /v1/bookings/{bookingId} (JSON, partial update). Set any of title/startsAt/endsAt/cancelled/noShow/timeZone/locale/units; use the fields passthrough for answers/linkFields or other documented fields. The path id is never sent in the body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bookingId | string | yes | The booking id to update (path only; required). |
| title | string | no | New booking title. |
| startsAt | string | no | New start time, ISO 8601 (reschedule). |
| endsAt | string | no | New end time, ISO 8601 (reschedule). |
| cancelled | boolean | no | Set true to cancel the booking, false to un-cancel. |
| noShow | boolean | no | Mark the attendee as a no-show (true) or not (false). |
| timeZone | string | no | New IANA time zone. |
| locale | string | no | New locale. |
| units | integer | no | New number of slot units. |
| fields | object | no | Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above. |
MUTATES YouCanBookMe data: cancels a booking. Convenience wrapper for PATCH /v1/bookings/{bookingId} with { cancelled: true } — safer and reversible (re-activate via update_booking cancelled=false) versus deleting. Returns the updated booking.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bookingId | string | yes | The booking id to cancel (path only; required). |
MUTATES YouCanBookMe data: updates a profile's (booking page) configuration. YCBM API: PATCH /v1/profiles/{profileId} (JSON, partial update). Pass the fields to change via the fields passthrough (e.g. { title, subdomain, ... }) — profile fields are numerous and use YCBM's own names. The path id is never sent in the body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id to update (path only; required). |
| fields | object | no | Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above. |
MUTATES YouCanBookMe data: adds an appointment type to a profile. YCBM API: POST /v1/profiles/{profileId}/appointmenttypes/items (JSON). Required: name; use the fields passthrough for description, slotLength, price, etc. The path profileId is never sent in the body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id (path only; required). |
| name | string | yes | The appointment type name (required). |
| fields | object | no | Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above. |
MUTATES YouCanBookMe data: updates an appointment type on a profile. YCBM API: PATCH /v1/profiles/{profileId}/appointmenttypes/items/{appointmentTypeId} (JSON, partial update). Pass changed fields (name, description, slotLength, price, ...) via the fields passthrough. Path ids are never sent in the body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id (path only; required). |
| appointmentTypeId | string | yes | The appointment type id to update (path only; required). |
| fields | object | no | Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above. |
MUTATES YouCanBookMe data: adds a team member to a profile. YCBM API: POST /v1/profiles/{profileId}/teammembers/items (JSON). Required: name; calendarId links the member to a calendar (find it via list_available_accounts). Use the fields passthrough for email, description, pic, etc. The path profileId is never sent in the body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id (path only; required). |
| name | string | yes | The team member's display name (required). |
| calendarId | string | no | The calendar id to link (see list_available_accounts). |
| fields | object | no | Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above. |
MUTATES YouCanBookMe data: updates a team member on a profile. YCBM API: PATCH /v1/profiles/{profileId}/teammembers/items/{teamMemberId} (JSON, partial update). Pass changed fields (name, email, description, calendarId, ...) via the fields passthrough. Path ids are never sent in the body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id (path only; required). |
| teamMemberId | string | yes | The team member id to update (path only; required). |
| fields | object | no | Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above. |
MUTATES YouCanBookMe data: adds a location to a profile. YCBM API: POST /v1/profiles/{profileId}/locations (JSON). Required: kind (location type) and strategy (how it is assigned). Use the fields passthrough for value, notes, and other documented fields. The path profileId is never sent in the body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profileId | string | yes | The profile (booking page) id (path only; required). |
| kind | string | yes | The location kind/type (required). |
| strategy | string | yes | The location assignment strategy (required). |
| value | string | no | The location value (e.g. an address or link). |
| notes | string | no | Notes shown with the location. |
| fields | object | no | Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above. |
- 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 Youcanbookme or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| list_bookings | no tags | |
| get_booking | untrusted-input | untrusted-input: keyword "fetch" |
| list_profiles | no tags | |
| get_profile | untrusted-input | untrusted-input: keyword "fetch" |
| list_team_members | no tags | |
| list_appointment_types | no tags | |
| list_locations | no tags | |
| list_available_accounts | no tags | |
| youcanbookme_request | no tags | |
| create_booking | state-write | state-write: declares destructiveHint: true |
| update_booking | state-write | state-write: declares destructiveHint: true |
| cancel_booking | state-write | state-write: declares destructiveHint: true |
| update_profile | state-write | state-write: declares destructiveHint: true |
| create_appointment_type | state-write | state-write: declares destructiveHint: true |
| update_appointment_type | state-write | state-write: declares destructiveHint: true |
| create_team_member | state-write | state-write: declares destructiveHint: true |
| update_team_member | state-write | state-write: declares destructiveHint: true |
| create_location | state-write | state-write: declares destructiveHint: 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
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 1.11.1.
No release note was published with this version.
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.
Any signed-in account that does not publish Youcanbookme can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.