A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Checkfront 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.
20
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Check Checkfront availability and rates, and manage booking sessions, bookings, customers and notes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http checkfront-mcp https://checkfront.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# checkfront_get_company, checkfront_list_categories, checkfront_list_items and 17 more
Checkfront 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 checkfront-mcp https://checkfront.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
20 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.
Fetch the connected Checkfront account's company configuration — name, URL, plan, currency, timezone, locale and date/time formats. A cheap way to confirm the host and credentials work. Checkfront: GET /api/3.0/company.
No parameter schema on file.
List the inventory categories (e.g. Tours, Rentals, Accommodations) with their ids, names, display order and item counts. Checkfront: GET /api/3.0/category.
No parameter schema on file.
List the enabled inventory items (tours, activities, rentals, rooms). With NO dates this is the plain catalogue. Pass start_date (and end_date / param quantities) to get a RATED response: per-item availability, pricing and a SLIP token — the SLIP is what checkfront_add_to_booking_session needs to book the item. Checkfront: GET /api/3.0/item.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | integer | no | Only items in this category. |
| keyword | string | no | Only items whose name contains this keyword. |
| item_id | string | no | Comma-separated list of item ids to filter to, e.g. 17,18. |
| available | integer | no | (rated) Only items with at least this many left in stock. |
| start_date | string | no | (rated) Booking start date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| end_date | string | no | (rated) Booking end date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| date | string | no | (rated) Alias of start_date for same-day bookings — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| start_time | string | no | (rated) Start time, for hourly bookings. |
| end_time | string | no | (rated) End time, for hourly bookings. |
| param | object | no | Booking parameters (quantities) keyed by the parameter ids configured in your account, e.g. {"adults": 2, "children": 1}. Sent as param[adults]=2. |
| discount_code | string | no | (rated) Discount code to apply to the price. |
| rules | string | no | 'soft' avoids date-based rule errors; 'off' disables rule checking. |
| packages | boolean | no | Include package options. |
Fetch one inventory item's details. Pass start_date / end_date and param quantities (e.g. {"adults": 2}) for a RATED response with availability (rate.status, rate.available), the price breakdown and the SLIP used to book it. For parent/child grouped items, rate the CHILD item. Checkfront: GET /api/3.0/item/{item_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | integer | yes | The item id. |
| start_date | string | no | (rated) Booking start date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| end_date | string | no | (rated) Booking end date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| date | string | no | (rated) Alias of start_date for same-day bookings — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| start_time | string | no | (rated) Start time, for hourly bookings. |
| end_time | string | no | (rated) End time, for hourly bookings. |
| param | object | no | Booking parameters (quantities) keyed by the parameter ids configured in your account, e.g. {"adults": 2, "children": 1}. Sent as param[adults]=2. |
| discount_code | string | no | (rated) Discount code to apply to the price. |
| rules | string | no | 'soft' avoids date-based rule errors; 'off' disables rule checking. |
| packages | boolean | no | Include package options. |
Day-by-day available inventory over a date range — for one item (item_ids with a single id), several items, or a whole category. Use it to answer 'which days next month still have space?'. Checkfront: GET /api/3.0/item/{item_id}/cal or GET /api/3.0/item/cal.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_ids | array | no | Item ids. One id queries that item's calendar; several query them together. |
| category_id | integer | no | Instead of item ids, a category of items. |
| start_date | string | no | Range start date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| end_date | string | no | Range end date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
List bookings, newest filters first — by status, customer, dates, item or partner. Each row has the booking code, status, totals (total, tax_total, paid_total), customer name/email, summary and date_desc. Paged (default 100/page); the response's request.pages tells you how many pages exist. Checkfront: GET /api/3.0/booking/index.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status_id | string | no | Booking status code, e.g. PEND, HOLD, PART, PAID, WAIT, STOP, VOID. |
| customer_id | integer | no | Only bookings for this customer id. |
| customer_email | string | no | Only bookings for this customer email. |
| start_date | string | no | Booking start (check-in) date. A date string or unix timestamp; prefix with '<' or '>' for before/after (e.g. ">2026-01-01"). |
| end_date | string | no | Booking end (check-out) date. A date string or unix timestamp; prefix with '<' or '>' for before/after (e.g. ">2026-01-01"). |
| created_date | string | no | Date the booking was created. A date string or unix timestamp; prefix with '<' or '>' for before/after (e.g. ">2026-01-01"). |
| last_modified | string | no | Date the booking last changed — useful for 'changed since' syncs. A date string or unix timestamp; prefix with '<' or '>' for before/after (e.g. ">2026-01-01"). |
| item_id | integer | no | Only bookings containing this item. |
| partner_id | string | no | Only bookings attributed to this partner account. |
| limit | integer | no | Bookings per page, 1-100 (default 100). |
| page | integer | no | Page number, starting at 1. |
Fetch extended information on one booking — status, dates, customer, form fields, line items and totals. Checkfront: GET /api/3.0/booking/{booking_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_id | string | yes | The booking code identifying the booking, e.g. CFPP-290317. |
List the notes left on bookings across the account (default: the past 30 days), each with its booking code, author account id (0 = customer), date, body and whether it is private. Checkfront: GET /api/3.0/booking/notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | Filter by a day (YYYY-MM-DD or ISO-8601) or a whole month (e.g. "2026-09"). |
Fetch the customer-details form for a booking (booking_form_ui): every field id (customer_name, customer_email, …), its label, type and whether it is required. Call this before checkfront_create_booking to know which form fields to send. Checkfront: GET /api/3.0/booking/form.
No parameter schema on file.
Read a booking session — the in-progress 'cart' — with its line items (keyed by line_id), dates, sub_total, tax, total and amount due. Checkfront: GET /api/3.0/booking/session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session_id returned by checkfront_add_to_booking_session. |
Look up customers by exact email, full name or phone number (exact matches; non-unique fields such as name can return several). Results are in the customers object. Checkfront: GET /api/3.0/customer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_email | string | no | Exact customer email address. |
| customer_name | string | no | Exact full name. |
| customer_phone | string | no | Exact phone number. |
| customer_id | string | no | Customer code/id. |
Fetch one customer's contact details and their bookings (codes with created dates). Checkfront: GET /api/3.0/customer/{customer_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The customer id (e.g. 25) or customer code. |
List the date-based events that change price or availability — seasonal rates (SE), specials (SP), discounts (DC), closures (status U) — with their dates, recurrence, pricing rule and the items/categories they apply to. Checkfront: GET /api/3.0/event.
No parameter schema on file.
List the staff (and partner) accounts on the Checkfront account — ids, names, emails, login ids and whether enabled. The account_id is what CHECKFRONT_ON_BEHALF takes. Checkfront: GET /api/3.0/account.
No parameter schema on file.
Start or modify a booking session: add one or more SLIPs (from a rated checkfront_get_item / checkfront_list_items call), replace a line with a new SLIP (line_id + slip), or alter lines (quantity, 'remove', 'optin'/'optout' for package add-ons). Holds the inventory while the session is open; NOTHING is booked until checkfront_create_booking. Returns the session_id to reuse. Checkfront: POST /api/3
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | no | Existing session to modify. Omit to start a new session. |
| slip | array | no | One or more SLIP strings to add, e.g. ["18.20171005X1-adults.1-children.0"]. |
| line_id | string | no | With a single slip: the session line to REPLACE with it (to change a regular item's options). |
| alter | object | no | Changes keyed by line_id, e.g. {"3": 5, "2.1": "optin", "1": "remove"} (a number sets the quantity). |
Abandon a booking session: 'clear' empties its items, 'end' closes it. Releases the inventory it was holding; no booking is affected. Checkfront: POST /api/3.0/booking/session/clear or /booking/session/end.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session to clear or end. |
| action | string | no | 'end' (default) closes the session; 'clear' empties it. |
Commit a booking: from a session_id (built with checkfront_add_to_booking_session) or directly from SLIPs, plus the customer form fields (see checkfront_get_booking_form for which are required — typically customer_name and customer_email). Creates a real reservation that consumes inventory and may notify the customer; change it later with checkfront_update_booking_status. Returns the new booking's
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | no | The session holding the items to book. |
| slip | array | no | Instead of a session: SLIP strings to book directly. |
| form | object | yes | Customer form fields, e.g. {"customer_name": "John Smith", "customer_email": "john@example.com"}. Sent as form[customer_name]=…. |
Set a booking's status — e.g. confirm a pending booking (PAID/PART), put it on HOLD or WAIT(list), or cancel it (VOID/STOP). Reversible: set it back to the previous status the same way. Does NOT record a payment. Optionally triggers the account's customer notifications. Checkfront: POST /api/3.0/booking/{booking_id}/update.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_id | string | yes | The booking code identifying the booking, e.g. CFPP-290317. |
| status_id | string | yes | The new status code. Defaults: PEND, HOLD, PART, PAID, WAIT, STOP, VOID (plus any custom statuses in Manage > Layout > Statuses). |
| notify | boolean | no | Send the account's notifications for this change (default false). |
Add a note to a booking, logged under the staff account the API acts on behalf of. Checkfront: POST /api/3.0/booking/{booking_id}/note.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_id | string | yes | The booking code identifying the booking, e.g. CFPP-290317. |
| body | string | yes | The note text, up to 3000 characters. |
Mark a guest as arrived (check in) or departed (check out). Checkfront adds a note under the acting account. VOID and cancelled bookings cannot be checked in or out. Checkfront: POST /api/3.0/booking/{booking_id}/checkin or /checkout.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_id | string | yes | The booking code identifying the booking, e.g. CFPP-290317. |
| action | string | no | 'checkin' (default) or 'checkout'. |
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 Checkfront 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.11.1.
1.11.1
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 Checkfront 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.