This integration summary explains Hospitable’s public MCP documentation. For the customer interview and reported thermostat launch results, see the Hospitable thermostat case study.
Hospitable lets AI clients read connected device status and operate smart locks through its MCP server. Its May 20, 2026 announcement describes lock actions that wait for confirmation from providers including Schlage, Yale and August through Seam. Hospitable's announcement
The job
A property operator needs to check a door, identify an offline device or let someone into the right property. Hospitable exposes these tasks alongside its existing property and reservation tools, so an AI client can work with that context. The account needs the Smart Devices entitlement and connected property devices. Setup and available tools
The published architecture
AI client → Hospitable MCP → lock/unlock tools
Device connection: Schlage, Yale and August through Seam.
This diagram summarizes the published interfaces and relationships. It does not reconstruct Hospitable's internal services.
| Tool | Published behavior |
|---|---|
get-property-devices | Lists property-linked locks and thermostats with available device state. |
lock-smartlock | Requests locking and waits for provider confirmation before returning the updated state. |
unlock-smartlock | Requests unlocking with the same confirmation behavior. |
Hospitable's May announcement documents these three tools. Its current reference, checked September 14, 2026, still lists them. These sources do not report a deployment-time comparison, action latency or financial return.
Device and account boundaries
The supported model and connection method matter. Hospitable's lock list names the Schlage Encode family and specific Yale and August models, with required apps and accessories. Its thermostat list identifies compatible models separately. The listed thermostat operation is reading device status through get-property-devices.
Build a similar workflow
Keep property selection and authorization in your application. Before issuing an action, resolve the intended property and device, then check its capabilities. Show the action's confirmed result or failure to the user. A request accepted by an API and a completed physical action are different states; Seam's Action Attempts describe how to track that distinction.
For your own Next.js app, load Seam's implementation-next_app_router_full_api reference through the documentation MCP: call get_prompt, then get_prompt_context. It keeps your workspace API key on the server and includes device reads and action-status checks. Add your application's user authorization before deploying it.
For scheduled guest access, start with Access Grants. That is a separate job from the immediate lock and unlock tools described here.
Based on Hospitable's public documentation, checked September 14, 2026.