lilo Vacation Rentals

io.github.lilo-propertyPublished by GitHub account lilo-propertyv1.1.0Updated Oct 24, 2026

Vacation rental discovery, direct booking, and property protection for AI agents.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an AI assistant discover vacation rentals, book them directly, and access property protection services.

What you can do
Search and discover vacation rental properties for a trip or stay. Book rentals directly through the assistant rather than a separate booking flow. Access property protection offerings tied to the rentals. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when you want an assistant to help find and book vacation rental stays, or to look into property protection for a rental, without leaving the conversation.
Requirements
A remote MCP endpoint at mcp.lilo.property, reachable over the network. An API key sent in the X-API-Key header is required; the key is obtained from the provider's developer page. No local runtime or packages are needed.
Before you install
The server requires an API key in the X-API-Key header, so treat it as a secret and avoid exposing it in logs or shared configs. Booking actions may create real reservations or commitments, so confirm details before letting an assistant complete a booking.

Installation

In SourceWeft

  1. Open lilo Vacation Rentals in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lilo-property%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lilo-vacation-rentals": {
      "type": "http",
      "url": "https://mcp.lilo.property/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

39% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.