Seam

@seam list all smart locks in the downtown office space and show which ones are currently locked

Found 8 devices in the downtown office space. 6 are currently locked: Front Door (Yale Assure Lock 2, locked), Conference Room A (August Smart Lock Pro, locked), Server Room (Schlage Encode Plus, locked), Executive Suite (Kwikset Halo, locked), Storage Closet (Yale Assure Lock SL, locked), Side Entrance (August Smart Lock, locked). 2 are unlocked: Break Room (Yale Assure Lock, unlocked since 9:14 AM), Loading Dock (Schlage Encode, unlocked since 8:02 AM). All devices report healthy battery levels above 60%.

This read-heavy example demonstrates device listing with real-time lock status. Requires the connected account to have granted device-read permissions. Lock state reflects the moment of the API call; physical state may change between query and response. Seam's device list supports filtering by space, manufacturer, or custom metadata fields.

@seam create a temporary access grant for contractor@example.com to unlock the loading dock from January 15-17, generate a PIN code

Access grant created successfully. Contractor identity created for contractor@example.com. PIN code 4729 generated and synced to Loading Dock (Schlage Encode). Grant active January 15, 2025 12:00 AM through January 17, 2025 11:59 PM UTC. The contractor can use PIN 4729 at the loading dock keypad during this window. Grant UUID: ag_abc123def456. Action attempt status: pending (PIN provisioning to device in progress, typically completes within 30 seconds).

This write example shows access-grant creation with PIN method. The grant provisions asynchronously—check action-attempt status to confirm the PIN reached the lock. If the device is offline, provisioning queues until reconnection. Deleting the grant before the end date will immediately revoke the PIN. Time-bound grants require the lock's firmware to support scheduled access.

@seam review all failed action attempts from the past 48 hours and summarize what went wrong with each device

Found 3 failed action attempts in the past 48 hours. (1) Conference Room A lock (August Smart Lock Pro): PIN creation failed due to 'device_disconnected'—lock was offline from 2:14-3:42 PM on Jan 12, retry succeeded automatically. (2) Executive Suite lock (Kwikset Halo): Access grant deletion failed with 'insufficient_permissions'—connected account lacks admin scope, requires re-authentication. (3) Front Door lock (Yale Assure Lock 2): Unlock command timed out, lock reported low battery (18%) and went offline mid-operation. Recommend battery replacement and retry.

This synthesis example pairs Seam's action-attempt log with AI reasoning to diagnose failure patterns. Action attempts track every async operation (PIN sync, lock/unlock commands, grant provisioning). Failures surface connectivity issues, permission gaps, or device-health problems. Seam retries some failures automatically; others require manual intervention like re-auth or hardware maintenance.

When Seam handles desk-booking access at scale

A 12-person coworking operator runs three locations with smart locks on private offices and meeting rooms. Members book desks through a custom portal; the ops team needs to issue door codes and mobile keys without touching physical hardware. Seam wins here because one Create Access Grant call provisions PIN and mobile-key methods across multiple devices, and List Access Grants filters by customer or space to audit who has access where. The API-key auth is simple enough for a solo dev to wire up in a weekend. If your access patterns change hourly (hot-desking with 90-minute slots), you'll burn through rate limits and need to batch grant creation. For daily or weekly bookings, Seam keeps your ops team out of the lock-management weeds.

Why Seam fits short-term rental handoffs

A two-person property management company handles 18 Airbnb units with August and Schlage smart locks. Every checkout triggers a Delete Access Grant to revoke the departing guest's code; every check-in creates a new grant with a time-bound PIN. The MCP's List Devices and List Connected Accounts tools let the team audit which locks are online and which provider accounts need re-auth, all from a shared Switchy chat. This scenario is Seam's sweet spot: the tool count is low, the workflow is repetitive, and the access-grant lifecycle maps cleanly to reservation start and end dates. If you manage long-term tenants who need permanent codes, the grant-delete cadence drops and you might not need the MCP at all—just set codes once in the Seam dashboard.

When Seam's action-attempt log saves debug time

A four-person facilities team at a 200-employee office uses Seam to manage conference-room locks and loading-dock gates. When an employee reports a door won't unlock, the team pulls List Action Attempts filtered by device UUID to see if the last grant-creation call failed or if the lock itself went offline. The MCP surfaces error codes and async operation status without switching to the Seam web console, cutting triage time from five minutes to thirty seconds. This works because the team already knows which device is misbehaving—they're not searching a 500-device inventory blind. If your building has more than 50 access points and incidents are rare, the overhead of keeping the MCP configured outweighs the triage speed gain. For teams handling daily access issues across a dozen devices, Seam's structured error log is worth the API-key setup.