Build with OpenClaw. Build access, climate, and sensor workflows.
Bring Seam’s current documentation into your OpenClaw workspace. Build the application logic for access, climate, or sensor workflows, then verify the specific devices and actions you intend to support.
Illustrative sandbox workflow with OpenClaw: consult Seam documentation, prepare scheduled guest access, then confirm the sandbox result. Access runs from Friday at 3 PM until Sunday at 11 AM. The door remains locked. No live device is operated.
Set up Seam in OpenClaw.
Use OpenClaw’s MCP command on the installation that owns your agent’s connection, then test the server before starting a workflow.
Add Seam’s MCP server
With a current OpenClaw installation, add the endpoint over Streamable HTTP. Then open Settings → MCP and use its scoped config editor to set auth: "oauth" on mcp.servers.seam. Select Sign in and complete browser authorization on the Gateway’s Settings page.
Probe the connection
After sign-in, run the live check and confirm the documentation tools and api_request are available. If your agent runs on a separate Gateway, refresh or restart that runtime after changing its configuration.
A saved server entry is only configuration; this probe checks that the endpoint responds.
Set up the project workspace
Give the agent access to your application’s project and paste this prompt. Follow /agents.md to set up a sandbox workspace and choose how your application or agent will make Seam API requests.
Seam agent setupAfter signing in, check that api_request appears alongside the documentation tools. Ask your agent to list your workspaces. If Seam returns a permission-consent link, open it, select the intended scope and Viewer for read-only access, then retry. Device changes require write permissions. No Seam API key belongs in this MCP configuration.
Already connected? Replace the old Seam entry instead of adding a duplicate, reconnect or restart your client, and start a new conversation to refresh its tools. For documentation and skill packs without sign-in, use https://mcp.seam.co/mcp instead and skip OAuth login. This optional anonymous connection cannot access workspace resources.
Read the MCP guideTroubleshoot with your agent.
Investigate device and connected-account issues, Access Grants, access codes, and API or authentication errors. Seam’s MCP delivers the troubleshooting skill pack directly to your agent, with playbooks for gathering evidence and identifying what is still unknown.
Connect with Viewer access.
Use an MCP client that supports OAuth to connect to Seam’s authenticated endpoint. Sign in and approve Viewer access to the workspace you want to investigate. Refresh the connection and start a new conversation to load its tools.
Use your existing workspace. This skill is available through MCP without a separate plugin install. Replace the placeholders with the affected resource, workspace, and incident time. The investigation uses public API evidence and stays read-only.
Set up troubleshootingPrompts to try.
Give OpenClaw a concrete task, ask it to check current documentation, and review the result.
Build a request-to-access workflow
Prepare a thermostat workflow
Route sensor events through the app
Questions.
Client setup references
OpenClaw MCP setup ↗OpenClaw skills ↗Seam agent setup ↗Seam integration skills ↗Where should I add the connection?
Add it on the installation or Gateway that owns the active agent runtime. OpenClaw documents that a reload in one CLI process does not automatically reload a Gateway running elsewhere. Probe the connection where the agent will use it.
Can OpenClaw load the Seam skills?
Yes. OpenClaw supports SKILL.md directories in the agent’s workspace skills/ and .agents/skills/ folders. Copy the relevant Seam skill directories with their supporting files into the intended workspace and confirm discovery for that agent.