Workflow Automation · Seam + Claude
Seam MCP with Claude: Control Smart Locks and Building Devices in Plain Language
The short answer
Claude works with Seam through the Model Context Protocol (MCP), a secure standard that lets Claude use software with permissions you control. Once connected, Claude can list devices, read sensor state, create access codes, unlock doors and adjust thermostats, all through natural language requests from your team.
What is Seam?
Seam is a connected device platform for smart locks, access systems, thermostats, sensors and other workspace devices. It gives developers one consistent interface to manage building access and device state across many hardware brands, so they do not need a separate integration for every manufacturer. Property managers, workplace teams, co-working operators, facilities teams and software companies building on top of physical spaces typically use Seam to run their buildings digitally.
How Claude connects to Seam through MCP
The Model Context Protocol is an open standard that acts like a universal adapter between Claude and other software. It lets Claude securely read information from a tool and take actions in it, using only the access your organisation grants. For Seam, this means Claude can work with your connected devices without anyone needing to learn the underlying technical interface.
Once connected, Claude can typically list the devices in your portfolio, check whether a door is locked, read the latest sensor readings and review thermostat settings. It can also carry out actions such as creating a time-limited access code for a visitor, unlocking a door for an approved person or adjusting a thermostat. Your team simply describes what they need in ordinary language.
Permissions and approvals keep people in charge. Access is set up with least-privilege rules, so Claude only reaches the devices and actions you allow. Consequential steps, such as issuing codes for new people or unlocking sensitive doors, can require a human to confirm first. Every action is recorded in an audit log so you can see who asked for what and when.
What you can automate
Visitor Access Codes
A receptionist asks Claude to create a temporary access code for a contractor visiting on Thursday between 9am and 1pm. Claude checks the device list, creates the code for the correct lock and confirms the validity window. The code expires automatically, reducing manual key handling and the risk of forgotten credentials.
Facilities Status Checks
A facilities manager asks each morning which doors are unlocked or which sensors have reported unusual readings. Claude reads the current device state across the portfolio and returns a short summary of anything needing attention, so the team can act before problems grow.
Thermostat Adjustments for Comfort
An office operations lead notices complaints about a cold meeting room. They ask Claude to raise the thermostat in that room for the afternoon. Claude reads the current setting and adjusts it within the limits you have approved, saving time for the team.
Tenant and Staff Onboarding
When a new employee or tenant joins, HR or property staff can ask Claude to issue the correct access codes for their building and floor. Claude follows your standard rules, so the right people receive the right access on their first day.
Post-Visit Access Review
At the end of each week, a building administrator asks Claude to list all access codes that are still active. Claude returns a clear list, and the administrator removes any that are no longer needed, keeping access tight and well documented.
An end-to-end workflow: Visitor Access with Calendar and Ticketing Sign-off
TriggerA meeting request for an external visitor is created in Microsoft 365 with the building entrance selected.
Claude reads the meeting details from Microsoft 365, including the visitor name, date and time.
Claude checks the ticketing system to confirm the host has submitted an access request and that it has been approved.
Claude asks the building administrator to confirm the request in the approval step.
Once approved, Claude creates a time-limited access code in Seam for the entrance lock, valid only during the meeting window.
Claude sends the code to the host and logs the action in the audit trail.
When the window closes, the code expires automatically and Claude records the closure.
OutcomeVisitor access is granted only for approved meetings and only for the required time. Typical results include fewer manual key requests, faster arrival for guests and a complete record of who accessed the building.
How we set it up
Free Automation Audit
We review how your team currently manages building access, devices and facilities requests. We identify the workflows worth automating and agree on the outcomes you want, at no cost.
Secure Connection with API Key
We connect Claude to Seam using an API key, the sign-in method Seam supports. The key is stored securely and scoped to the minimum access needed, with no more device control than your workflows require.
Workflow Design and Approvals
We design the end-to-end workflow across Seam and your other systems, such as Microsoft 365, your CRM or ticketing tool. We define which actions need human approval and set the rules for codes, unlocks and thermostat limits.
Testing and Launch with Monitoring
We test the workflow against real past cases, including edge cases such as expired codes and offline devices. After launch we monitor performance and keep audit logs in place.
Team Training and Handover
We train your staff to make requests in plain language and to review approvals. We provide clear documentation so your team can run the workflow confidently and we can refine it as your portfolio grows.
Who benefits
- Property or Facilities Manager
- Check device status and issue access quickly without travelling to each site.
- Workplace or Office Operations Lead
- Handle visitor access and comfort requests through simple requests instead of manual processes.
- IT or Security Lead
- Keep control through least-privilege access, approvals and a full audit trail.
- Software Team Building on Physical Spaces
- Add natural language control to products without building each hardware integration by hand.
Security and control
- Least-privilege API access so Claude reaches only the devices and actions you approve.
- Human approval for consequential actions such as issuing codes for new people or unlocking sensitive doors.
- Time-limited access codes that expire automatically to reduce the risk of lingering credentials.
- Complete audit logs recording every request, action and approval.
- Regular reviews of connected devices, permissions and active codes to keep access current.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to align with their own data protection obligations. Businesses in India must consider the Digital Personal Data Protection Act, 2023, and we help select hosting that supports those requirements. Organisations in the UAE and Saudi Arabia must meet local data protection laws, and we design the workflow with appropriate hosting. Hosting region is chosen to meet your specific legal and contractual requirements, and we advise on this during the audit.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Seam MCP server do?
The Seam MCP server lets Claude securely connect to your Seam account. It allows Claude to list connected devices, read their state, create access codes, unlock doors and adjust thermostats, all within the permissions you set. It acts as a secure bridge, so your team can use natural language instead of technical interfaces.
Is connecting Seam to Claude secure?
Security is built into the design. Access uses an API key scoped to the minimum permissions needed. Sensitive actions can require human approval, codes expire automatically, and every action is logged. We also review the setup against your own security policies before launch.
What can Claude actually do with Seam?
Typically, Claude can list your devices, check whether doors are locked, read sensor readings, create time-limited access codes, unlock doors for approved people and adjust thermostat settings. The exact actions available depend on your Seam setup and the devices you have connected.
How long does setup take?
Timing depends on the size of your portfolio and the workflows you choose. A focused single-workflow setup is often completed within a few weeks, including audit, testing and training. Larger multi-site deployments take longer. We confirm the timeline during the free audit.
What permissions or account access do I need?
You will need an active Seam account with an API key that we can scope to the devices and actions your workflows require. Your organisation decides which permissions are granted. We advise on the appropriate level during the audit so access stays limited to what is necessary.