Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Workspace 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
Floreal Holidays Belgium: live prices and availability; staff run M&E dossiers, day sheets, tasks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http florealholidays-workspace-mcp https://mcp.florealholidays.be/mcp
# 2 — ask your agent for something these tools do
# list_locations, search_stays, get_stay_price and 13 more
Workspace 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 florealholidays-workspace-mcp https://mcp.florealholidays.be/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.
16 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.
All Floreal Holidays locations in Belgium with their slug, name, kind of site, town, region and coordinates. Use the "slug" as the domain argument of every other tool. The "type" is the kind of site, not the accommodation on it — a park can offer hotel rooms, studios, apartments, chalets and camping pitches at the same time; ask list_accommodation_types for that. Locations with bookable=false (t
No parameter schema on file.
Find where Floreal Holidays has a stay available, across every location in one call, with the live all-in price per accommodation type. Use this whenever the guest has not picked a location yet — "somewhere at the Belgian coast in July", "a hotel room in the Ardennes with a dog", "the cheapest week for a family of four". Narrow with region (coast, ardennes, kempen, gaume, wallonie-picarde), with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| arrival | string | yes | Arrival date (YYYY-MM-DD) |
| nights | integer | yes | Number of nights |
| adults | integer | yes | Number of adults |
| children | integer | no | Number of children (under 12) |
| babies | integer | no | Number of babies (under 2) |
| pets | integer | no | Number of pets |
| region | string | no | Region to limit the search to: coast, ardennes, kempen, gaume, wallonie-picarde (Dutch/French names work too) |
| domains | array | no | Location slugs to limit the search to; takes precedence over region |
| accommodation | string | no | Accommodation kind (hotel_room, studio, apartment, chalet, mobile_home, glamping, camping_pitch) or a word from the type name, e.g. "hotel", "apartment", "chalet", "tent" |
| maxPrice | number | no | Highest acceptable all-in price for the whole stay, in euro |
| flexibleDays | integer | no | Also search this many days before and after the arrival date, in the same call (0 = that day only). Use it for "around the 12th" or "some weekend in July". When the exact date has nothing, the tool al |
| lang | string | no | Language for accommodation names; defaults to Dutch, the language they are maintained in |
Live all-in price and availability for a stay at one Floreal location, per accommodation type, for the given arrival date, number of nights and party. Each option carries its kind (hotel room, studio, apartment, chalet, glamping, camping pitch) and how many people it sleeps. Pass a packageId from list_arrangements to price that specific package. With flexibleDays the same call also prices the days
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Location slug from list_locations, e.g. "floreal-blankenberge" |
| arrival | string | yes | Arrival date (YYYY-MM-DD) |
| nights | integer | yes | Number of nights |
| adults | integer | yes | Number of adults |
| children | integer | no | Number of children (under 12) |
| babies | integer | no | Number of babies (under 2) |
| pets | integer | no | Number of pets |
| packageId | string | no | Package id from list_arrangements (optional) |
| flexibleDays | integer | no | Also search this many days before and after the arrival date, in the same call (0 = that day only). Use it for "around the 12th" or "some weekend in July". When the exact date has nothing, the tool al |
| lang | string | no | Language for accommodation names; defaults to Dutch, the language they are maintained in |
What kinds of accommodation one Floreal Holidays location offers — hotel rooms, studios, apartments, chalets, glamping, camping pitches — each with how many people it sleeps and an indicative "from" price. Use this for questions about what a location has ("does Blankenberge have hotel rooms?", "are there apartments in Nieuwpoort?"). A location can combine several kinds. Without a date it probes th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Location slug from list_locations, e.g. "floreal-blankenberge" |
| arrival | string | no | Optional sample arrival date; omit to probe the next two months (YYYY-MM-DD) |
| lang | string | no | Language for accommodation names; defaults to Dutch, the language they are maintained in |
The bookable packages of one location: stay arrangements and add-on extras, with name, description and validity period. A package price depends on the stay and the party, so ask for it with get_stay_price and the packageId from this list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Location slug, e.g. "floreal-blankenberge" |
The current restaurant and food & beverage menus of one Floreal location, as published by that location. Not every location publishes menus.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Location slug, e.g. "floreal-blankenberge" (see list_locations) |
| lang | string | no | Menu language (defaults to Dutch) |
Published questions and answers about Floreal Holidays, optionally narrowed to one location. Answers are multilingual (Dutch, French, English).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | no | Location slug; omit for the general questions |
Information about Floreal Holidays gift cards: amounts, languages and where to buy one. Gift cards are valid at every location.
No parameter schema on file.
Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns who you are and which locations you may look at. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.
No parameter schema on file.
Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns occupancy, revenue and KPIs per day, month or year. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.
No parameter schema on file.
Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns the reservations arriving on a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.
No parameter schema on file.
Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns the reservations departing on a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.
No parameter schema on file.
Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns reservations in a date window, by room or booking number. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.
No parameter schema on file.
Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns one reservation: dates, party size, room, status. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.
No parameter schema on file.
Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns arrivals, departures and guests in house for a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.
No parameter schema on file.
Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns tasks per department and status. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.
No parameter schema on file.
- 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 Workspace 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.
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. 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 0.8.0.
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 Workspace 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.