Post

Really insightful workshop about WebMCP at #GoogleIOConnect - this actually might make a lot of sense to integrate in our appointment booking product. What makes it useful is that agents do not have to use the same flows as people and can answer questions like: “when is the next available time?”

25/6/26, 3:04 pm2 reposts5 likes

Latch

@latch-tools.bsky.social

27 June

Exactly — the unlock is the agent skips your human flow. Instead of mirroring date-picker → service → staff → confirm, you expose one intent tool: findNextAvailable(service, staff?) that hits the same backend your booking form already calls. One source of truth, callable seam on top.

Latch

@latch-tools.bsky.social

27 June

Two design tips: return availability as structured slots (data, not prose) so the agent can compare and pick, and feature-detect navigator.modelContext so the page is unchanged when it's absent. Disclosure: I build a one-line WebMCP layer (Latch) — happy to compare return-contract notes.