Slipstream: short term rental analytics

rentals.slipstream由 slipstream.rentals 发布官方发布者v1.0.1更新于 Nov 6, 2026

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

已验证Streamable HTTP可网页运行数据与分析商业与电商

服务详情

标识符: rentals.slipstream/slipstream
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Oct 30, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 slipstream.rentals，且该域名同时运行其端点。这可以确认发布者，但并不代表该服务的工具是安全的。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/rentals.slipstream%2Fslipstream.svg)](https://sourceweft.com/mcp/rentals.slipstream%2Fslipstream?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

面向短租房东的只读分析：预订、入住率、预测、评价与业主结算，并附回原始页面的链接。

可以做什么: 查看数据新鲜度、列出房源，读取房东目标与按优先级排序的下一步动作
汇总预订、入住率、空置夜、房源设置与未来收入预测
按类别读取评价、房源亮点与各房源评价概况
检查资金问题、业主付款、每次入住成本，并将业主账单与预订核对
解释和说明已启用配方的工作方式、存储输出与历史命中记录
为某房源生成回头客优惠草稿
适用场景: 适合希望让助手直接回答自家房源组合问题的短租房东、共同房东与管理者，例如入住率、定价缺口、评价趋势、付款与账单差异，无需导出表格。
运行要求: 远程 streamable HTTP 服务器，使用公开的 Slipstream 地址，无需本地安装。需用 Slipstream 账户（试用或付费）通过 OAuth 登录；共同房东和管理者账户可连接，业主账户暂不支持。未登录可查看工具列表，但每次调用工具都需已登录账户。

安装前请注意

登录后助手可读取房东经 Hospitable、OwnerRez 或 Hospitable Connect 接入的 Airbnb 等短租数据。工具均为只读，不能修改房源、价格或设置，也不能发送消息，且不返回客人姓名、邮箱和电话。调用记录保留 90 天，可在 Slipstream 设置中查看或断开连接。

安装

在 SourceWeft 中

打开控制台中的 Slipstream: short term rental analytics，将其添加到工作区。
连接所需的凭据。它们会被私密存储，绝不会在公开页面上展示。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/rentals.slipstream%2Fslipstream/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。客户端会在首次连接时完成 OAuth 登录。

{
  "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.

Server URL: https://slipstream.rentals/api/ask/mcp (streamable HTTP)
Sign-in: OAuth with a Slipstream account (trial or paid). Co-host and manager accounts can connect; owner accounts can't yet.
Registry name: rentals.slipstream/slipstream (server.json)
Product page: https://slipstream.rentals/integrations/claude?ref=github

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:

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

Tool	What it reads
`get_data_status`	How fresh the data is: when the last full sync with the PMS completed, and whether its bookings and reviews fetched cleanly.
`list_properties`	The properties this viewer can see, with their ids.
`get_goals`	The host's goals: each goal's sentence, current reading, target and gap.
`get_next_moves`	The ranked list of moves that matter most now: money errors first, then open nights, then Top Priorities, then goals.
`get_reservations_summary`	Booked 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_occupancy`	Occupancy 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_nights`	Unbooked 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_settings`	The 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_forecast`	Expected 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_metric`	One named metric for each property (or one property).
`get_recipe_output`	The 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_summary`	Reviews 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_categories`	Reviews 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_highlights`	What 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_checks`	Money 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_payouts`	What owners earn.
`get_cost_per_stay`	Consumables (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_month`	One 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_value`	How a docked recipe computed one output for one property: each step in order, with its value and what it reads.
`track_record`	What 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_draft`	Open 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_recipe`	How 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_bookings`	Check 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:

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

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.