<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/04a148ac1d824d188543a514e14eed66&quot; frameborder=&quot;0&quot; width=&quot;1860&quot; height=&quot;1395&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1395</height><width>1860</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1395</thumbnail_height><thumbnail_width>1860</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/04a148ac1d824d188543a514e14eed66-59995dec588f627d.gif</thumbnail_url><duration>116.889</duration><title>Using an MCP to close software gaps [captions fixed]</title><description>This Loom explains how to use an MCP with Claude to fill gaps in software workflows, using Hospitable as the example. The speaker connects Hospitable’s MCP to Claude in about a minute and then, after describing the need in plain English, has Claude build a skill in about 20 minutes that fetches reservations, blocks same-day turnovers, handles cancellations, and texts a summary to the speaker’s wife. Hospitable runs every morning and only updates new reservations needing attention, with calendar blocks showing the updates came from an MCP. The speaker emphasizes this no-coding workaround can help with other software that lacks needed features.</description></oembed>