Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
AegeanBot Direct Stays 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.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search verified Greek vacation rentals with live availability, prices, policies, and booking links.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aegeanbot-direct-stays-mcp https://app.aegeanbot.com/mcp
# 2 — ask your agent for something these tools do
# get_listing_policies, get_faq_answer, search_listings and 2 more
AegeanBot Direct Stays costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AEAll 1 server
aegeanbot1 server
1 category
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 aegeanbot-direct-stays-mcp https://app.aegeanbot.com/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
5 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.
Every policy fact for ONE listing in one call: check-in/out times, advance notice, preparation days, this month's minimum stay, cancellation policy, and (when configured) amendment rules like late checkout. Use for ANY rules/policy question about a home.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing | string | yes | listing title (partial ok) |
Retrieve the host's own Q&A entries most relevant to a factual question about the stay, the house, or the host's services. Prefer this over guessing for any host-specific question.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| listing_id | string | no | scope to one listing (optional) |
Search available vacation rentals across Greece. Pass explicit destinations, dates, guest counts and filters as structured fields; use query only for preferences not represented by another field. Do not invent locations, dates, guest counts or budgets the guest never gave. Results include stable listing ids for follow-up calls (get_listing_details, check_availability_and_price).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | optional free-text preferences NOT captured by the structured filters, e.g. 'quiet romantic vibe with sunset views' — do not repeat structured information here |
| location | string | no | a PLACE the guest actually named: city, island, region, island complex ('Cyclades') or area ('Athens south coast'). For generic geography ('the islands', 'the mountains', 'by the sea') use setting ins |
| setting | string | no | geography facet for generic wishes: 'στα νησιά'/'the islands' → island; combinable with budget/dates, replaces a location guess |
| mood | string | no | holiday-mood collection: beach=steps from the sea/coves, pools=private pool/resort calm, sunset=golden-hour terraces/romance, night=chora/town stays with evening life |
| guests | integer | no | total guests (alternative to adults/children when the split is unknown) |
| adults | integer | no | number of adult guests |
| children | integer | no | number of children — counted toward capacity together with adults |
| infants | integer | no | number of infants — noted but NOT counted toward sleeping capacity |
| bedrooms | integer | no | minimum bedrooms requested |
| bathrooms | number | no | minimum bathrooms requested |
| property_type | string | no | requested property type |
| amenities | array | no | hard amenity requirements the guest explicitly asked for — every listed amenity must be present |
| max_nightly_price | number | no | maximum accommodation price per night (EUR) |
| max_total_price | number | no | maximum total stay price (EUR) when the guest gave a whole-trip budget — only applied when exact dates are also given (otherwise ignored with a note) |
| currency | string | no | currency used for price filters |
| sort | string | no | result ordering; default recommended |
| checkin | string | no | exact arrival date YYYY-MM-DD — ONLY when the guest gave real stay dates. If they only named a month/season ('in August'), leave dates out: availability is checked per night, so a whole month demands |
| checkout | string | no | exact departure date YYYY-MM-DD — same rule as checkin |
| near_metro | boolean | no | true only when the guest wants to be near a metro/subway station (Athens & Thessaloniki only) — filters to homes within a 1 km walk of a station |
Full facts for ONE listing already in play (amenities, description, capacity, base price).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing | string | yes | listing title (partial ok) |
Exact availability + total price for one listing and concrete dates, with the direct booking link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing | string | yes | — |
| checkin | string | yes | YYYY-MM-DD — never in the past; bare day numbers in a follow-up ('26 to 29') keep the month/year already under discussion, NOT the current month |
| checkout | string | yes | YYYY-MM-DD |
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 AegeanBot Direct Stays 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. 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.0.0.
1.0.0
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 AegeanBot Direct Stays 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.