Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
Bookafy 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.
93/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Review appointments, customers and staff, and manage Bookafy bookings.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bookafy-mcp-by-usefulapi https://bookafy.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# bookafy_get_account, bookafy_list_appointments, bookafy_create_appointment and 12 more
Bookafy 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 598 servers
usefulapi598 servers
25 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 bookafy-mcp-by-usefulapi https://bookafy.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 account this API key belongs to: the admin user's email. Use it to confirm which Bookafy account is connected. GET /api/v3/me.
No parameter schema on file.
List the appointments of ONE staff member (identified by their email: take it from bookafy_list_staff), newest first, optionally within a UTC date range. Each item has the service, customer, start/end time (UTC), title, price, duration and status. Page with page/per_page (default 25). Cancel/reschedule tokens are never returned. GET /api/v3/appointments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| staff_email | string | yes | Email of the staff user whose appointments to list (from bookafy_list_staff). |
| from | string | no | Only appointments starting at or after this moment: yyyy-mm-dd (midnight UTC) or ISO 8601 date-time with timezone. |
| to | string | no | Only appointments ending before this moment: yyyy-mm-dd (midnight UTC) or ISO 8601 date-time with timezone. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
WRITE: book an appointment for a customer with a staff member and service (ids from bookafy_list_staff and bookafy_list_services). The customer is created from the given name/email/phone. Bookafy may email the booking confirmation to the customer and add the event to connected calendars, so only call it when the user clearly asked to book. Times are converted to UTC. POST /api/v3/appointments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| staff_user_id | integer | yes | Staff user id (from bookafy_list_staff). |
| service_id | integer | yes | Service id assigned to that staff user (from bookafy_list_services). |
| start | string | yes | Start, ISO 8601 date-time with timezone, e.g. 2026-11-02T09:30:00-05:00. |
| end | string | yes | End, ISO 8601 date-time with timezone (after start, at most 24 h later). |
| customer_name | string | yes | Customer's full name. |
| customer_email | string | no | Customer's email (the confirmation goes there). |
| customer_phone | string | no | Customer's phone number. |
| custom_fields | object | no | Custom booking-form answers as {field_name: value}, with underscores for spaces, e.g. {"What_is_your_DOB": "1990"}. |
| title | string | no | Title shown for the appointment (default: Bookafy's own). |
| description | string | no | Notes shown with the appointment. |
| price | number | no | Price of the appointment (default: the service's price). |
WRITE: reschedule or edit an existing appointment. Send the required staff, service, new times and customer name — read current values with bookafy_list_appointments first. Omitted optional fields are not sent. The customer may be notified of the change. Times are converted to UTC. PUT /api/v3/appointments/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appointment_id | integer | yes | Appointment id (from bookafy_list_appointments). |
| staff_user_id | integer | yes | Staff user the appointment is with. |
| service_id | integer | yes | Service id. |
| start | string | yes | New start, ISO 8601 date-time with timezone. |
| end | string | yes | New end, ISO 8601 date-time with timezone (after start, at most 24 h later). |
| customer_name | string | yes | Customer's full name. |
| customer_email | string | no | Customer's email. |
| customer_phone | string | no | Customer's phone number. |
| custom_fields | object | no | Custom booking-form answers as {field_name: value}, with underscores for spaces, e.g. {"What_is_your_DOB": "1990"}. |
| title | string | no | Appointment title. |
| description | string | no | Notes shown with the appointment. |
| price | number | no | Price of the appointment. |
WRITE, IRREVERSIBLE: delete (cancel) an appointment. Bookafy may notify the customer and remove the event from connected calendars, and the appointment cannot be restored through the API. Only call it when the user explicitly asked to cancel this appointment. DELETE /api/v3/appointments/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appointment_id | integer | yes | Appointment id (from bookafy_list_appointments). |
| staff_user_id | integer | yes | Staff user the appointment is with (its user_id). |
List the account's customers (id, name, email, phone and custom booking-form answers). Bookafy returns the whole list at once; use search (matches name, email or phone) and limit/offset to page through it. GET /api/v3/customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Only customers whose name, email or phone contains this text (case-insensitive). |
| limit | integer | no | Most customers to return, 1-500 (default 100). |
| offset | integer | no | Skip this many matches (default 0). Pass the previous reply's next_offset to read on. |
WRITE: add a customer record (name required; email, phone and custom booking-form answers optional). It does not book anything. POST /api/v3/customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Customer's full name. |
| string | no | Customer's email. | |
| phone | string | no | Customer's phone number. |
| custom_fields | object | no | Custom booking-form answers as {field_name: value}, with underscores for spaces, e.g. {"What_is_your_DOB": "1990"}. |
WRITE: change a customer's details. Bookafy needs the name every time, so pass the current name when you only change the email or phone. Fields you leave out are not sent. PUT /api/v3/customers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | Customer id (from bookafy_list_customers). |
| name | string | yes | Customer's full name (required by Bookafy on every update). |
| string | no | New email. | |
| phone | string | no | New phone number. |
| custom_fields | object | no | Custom booking-form answers as {field_name: value}, with underscores for spaces, e.g. {"What_is_your_DOB": "1990"}. |
List every service (appointment type) with id, name, price, duration, buffers, category, scheduling mode and online-meeting options. Use the ids when booking. GET /api/v3/services.
No parameter schema on file.
The appointment types grouped by category, each with its public booking-page link — use it to give a customer the link to book themselves. GET /api/v3/appointment_types.
No parameter schema on file.
List the staff users (id, name, email, booking-page URL). Use the id or email for appointments. GET /api/v3/staff_members.
No parameter schema on file.
List classes and one-off appointments with price, duration, location, seats, booking link and their sessions (date, seats total/filled/remaining, zoom link). GET /api/v3/classes.
No parameter schema on file.
One class with its sessions and the attendees booked on each (name, email, phone, booking time). Optional filters narrow the sessions. GET /api/v3/classes/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| class_id | integer | yes | Class id (from bookafy_list_classes). |
| price | number | no | Only sessions with this price. |
| duration | integer | no | Only sessions of this length in minutes. |
| attendee_name | string | no | Only sessions with an attendee of this name. |
| provider_name | string | no | Only sessions run by this provider. |
| from | string | no | Only sessions starting at or after this moment (yyyy-mm-dd or ISO 8601 date-time with timezone). |
| to | string | no | Only sessions ending before this moment (yyyy-mm-dd or ISO 8601 date-time with timezone). |
The attendees of one class session (name, email, phone). Get session ids from bookafy_list_classes. GET /api/v3/sessions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | integer | yes | Session id (sessionId in bookafy_list_classes). |
List the webhook subscriptions (id, callback URL, event type such as appointment_created or customer_updated). Read-only. GET /api/v3/api_subscriptions.
No parameter schema on file.
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 Bookafy 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: —
ATool-list grade · score 93 / 100
Release 1.7.2 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest9a58ac3e49d339683bfad08422eb1eff4407788c22260f36d3459cdafa552e34
Score vectorthreat 100 → client 93
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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 |
|---|---|---|
| bookafy_get_account | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_list_appointments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_create_appointment | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| bookafy_update_appointment | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| bookafy_cancel_appointment | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| bookafy_list_customers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_create_customer | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| bookafy_update_customer | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| bookafy_list_services | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_list_appointment_types | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_list_staff | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_list_classes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_get_class | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_list_session_attendees | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bookafy_list_webhooks | external-sinkuntrusted-input | external-sink: keyword "webhook"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest9a58ac3e49d33968
Scanned2026-11-07
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.7.2.
1.7.2
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 Bookafy 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.