Slipstream: short term rental analytics

rentals.slipstreamPublished by slipstream.rentalsOfficial publisherv1.0.1Updated Nov 6, 2026

Read-only analytics for short-term rentals: bookings, occupancy, forecasts, reviews, owner payouts.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Read-only analytics for short-term rental hosts: bookings, occupancy, forecasts, reviews and owner payouts, with links back to source pages.

What you can do
  • Check data freshness, list properties and read host goals and ranked next moves
  • Summarize reservations, occupancy, open nights, listing settings and revenue forecasts
  • Read reviews by category, listing highlights and review summaries per property
  • Inspect money checks, owner payouts, cost per stay and reconcile owner statements against bookings
  • Explain and describe docked recipes, their stored outputs and their track record
  • Open a repeat-guest offer draft for a property
When to use it
Useful for short-term rental hosts, co-hosts and managers who want an assistant to answer questions about their own portfolio — occupancy, pricing gaps, review trends, payout and statement discrepancies — without exporting spreadsheets.
Requirements
Remote streamable HTTP server at the published Slipstream URL; no local install. Requires OAuth sign-in with a Slipstream account (trial or paid); co-host and manager accounts can connect, owner accounts cannot yet. Tool listing works without login, but every tool call needs a signed-in account.
Before you install
Sign-in grants the assistant read access to the host's rental data from Hospitable, OwnerRez or Airbnb via Hospitable Connect. Tools are read-only and cannot change listings, prices or settings or send messages, and guest names, emails and phone numbers are not returned. Calls are logged for 90 days and connections can be reviewed or disconnected in Slipstream settings.

Installation

In SourceWeft

  1. Open Slipstream: short term rental analytics in the dashboard and add it to a workspace.
  2. Connect the required 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/rentals.slipstream%2Fslipstream/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "slipstream-short-term-rental-analytics": {
      "type": "http",
      "url": "https://slipstream.rentals/api/ask/mcp"
    }
  }
}

README

Slipstream MCP server

Slipstream connects AI apps to a short-term rental host's own data: bookings, occupancy, forecasts, reviews and owner payouts from Hospitable, OwnerRez or an Airbnb account connected through Hospitable Connect. Every tool is read-only, and every figure comes with a link to the Slipstream page it came from.

This repository holds the server's public metadata and test prompts. The server itself is hosted; there is nothing to install or run.

Add it

Claude: open Slipstream in Claude's connector directory and choose Connect. Or, in Claude, open Customize → Connectors → Add custom connector, and paste the server URL.

Claude Code:

sh
claude mcp add --transport http slipstream https://slipstream.rentals/api/ask/mcp

Any MCP client that supports remote servers with OAuth sign-in can connect the same way. initialize and tools/list answer without a login, so you can see the tools first; every tools/call needs a signed-in account.

Tools

ToolWhat it reads
get_data_statusHow fresh the data is: when the last full sync with the PMS completed, and whether its bookings and reviews fetched cleanly.
list_propertiesThe properties this viewer can see, with their ids.
get_goalsThe host's goals: each goal's sentence, current reading, target and gap.
get_next_movesThe ranked list of moves that matter most now: money errors first, then open nights, then Top Priorities, then goals.
get_reservations_summaryBooked stays grouped by check-in month, by channel, or by property: count, nights, revenue and average lead time (days from booking to check-in), then cancelled bookings and their revenue over the same span and groups.
get_occupancyOccupancy for one or more calendar months, per property and for the portfolio: nights booked within those months (stays crossing a month's edge counted only for their nights inside it), nights in the period, and the open nights left.
get_open_nightsUnbooked nights right after a checkout in the next 14 days, per property, ranked by what they could earn (nights × recent nightly rate), with the minimum stay that limits selling them.
get_listing_settingsThe pricing and availability settings last read from the PMS for each property: base and weekend nightly price, minimum stay, preparation time, cleaning fee per channel, and settings changes in the last 90 days.
get_forecastExpected revenue for months from now on, with what is booked, what usually still comes in, the same month last year, the range, and how often that range held in past forecasts.
get_metricOne named metric for each property (or one property).
get_recipe_outputThe latest stored outputs of a docked recipe (Top Priorities, Booking Pace Sentinel, The Pricing Oracle, The Maintenance Prophet, Reviews Owed, Fee Gaps and the rest) for each property, with when each was computed and what data the recipe reads.
get_review_summaryReviews per property: share of eligible stays reviewed (with its 95% range and how it compares with the account), stays still owed a review, the rating trend, and the complaint group costing the most stars.
get_review_categoriesReviews by category per property (cleanliness, broken items, noise, check-in, Wi-Fi, value and the rest): the stars per rated review that guests' complaints about each category cost, how many reviews complain about it and how many praise it, plus the categories guests praise most.
get_listing_highlightsWhat one property offers that a listing title or description could lead with: bedrooms, guests it sleeps, property type and town; its most valuable amenities; amenities it has that the listing text never mentions or mentions only in passing; and what guests praise most in reviews.
get_money_checksMoney correctness per property: bookings missing a fee the property normally charges, double bookings and duplicate records, open owner incidents (refunds and over-limit charges), whether an owner split is set, and whether statements are on file for reconciliation.
get_owner_payoutsWhat owners earn.
get_cost_per_stayConsumables (supplies) and housekeeping cost per stay per property, from the owner statements on file: the latest month's figure over a trailing three months, the usual figure lately, whether the latest month is a spike against the property's own history, and the published range for comparison.
check_statement_monthOne month's owner statement against the bookings, per property: how many bookings the statement lists, statement lines for bookings the PMS doesn't have, that month's bookings missing from the statement, bookings whose rent differs between the two, and open guest refunds from that month and whether the statement carries them.
explain_valueHow a docked recipe computed one output for one property: each step in order, with its value and what it reads.
track_recordWhat has been checked against outcomes: each recipe's matured predictions and how many held, the changes this host logged with how each was scored, and the recipe forecasts being tracked against what happens.
open_draftOpen the repeat-guest offer for a property: past guests whose reviews said they'd return, matched to an email, with a draft offer the host edits and sends from the property page.
describe_recipeHow a docked recipe works, without running it: each step in order, what it does, the steps it reads from, and the stored fields and data sources it reads.
check_statement_against_bookingsCheck an owner statement the user pasted or attached (from a property manager or co-host) against this account's own bookings for that property.

What it never does

  • It can't change a listing, a price or a setting, and it can't send messages.
  • Guest names, emails and phone numbers are never returned.
  • Reads cost nothing in Slipstream credits.
  • Settings → Connected AI apps in Slipstream lists each connection, when it was last used and what it read, with a Disconnect button. Calls are logged for 90 days.

Test prompts

prompts.md is the set used to check that a model picks the right tool from these descriptions, including requests it should decline.

ChatGPT plugin package

openai-plugin/ is the package for OpenAI's Plugin directory: plugin.json (listing, review test cases), mcp.json (the one server) and the icons. To build the ZIP:

sh
cd openai-plugin && zip -X -r ../dist/slipstream-openai-plugin-1.0.0.zip plugin.json mcp.json assets

mcp.json holds only the server URL: the Agent Plugins schema rejects anything else on an HTTP server, so OAuth is chosen in the portal. No credentials go in the package; reviewer sign-in is entered in the dashboard.

Contact

[email protected]

Source: README.md at commit a0141e0

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestOct 30, 2026

Score

75% 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
  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Slipstream integrations