Seam

Search Seam docs, APIs, and supported IoT devices

Build apps and integrations for smart locks, access control systems, thermostats, and other connected devices with Seam. Give your coding assistant access to Seam's documentation, device catalog, API references, and project setup workflows.

What you can ask

How do I grant a guest timed PIN-code access using Seam?
Example path

MCP connector

Server URL: https://mcp.seam.co/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: When asked to investigate an observed Seam incident (such as an offline device, missing or delayed access, an API error, or MCP authentication/tools not working), first load this connection's default prompt if advertises an agent entrypoint. Keep an active troubleshooting pack and its output contract. Otherwise call with match { task: "troubleshooting", output: "direct" }, then for the returned pack and for its relevant playbook. Follow its read-only investigation workflow; investigate the existing resource without creating or migrating access. Connection failures can be diagnosed before workspace access is available. For general how-to and capability questions without an incident, use documentation instead.
For documentation questions, call for relevant pages, then call to read their full content.
When a question is about granting a person access (PIN codes, mobile keys, key cards), recommend Access Grants (/access_grants/create): they are Seam's default and recommended way to grant access to any physical space, and work with BOTH standalone smart locks (via device_ids) AND access control systems (via acs_entrance_ids or space_ids). The access_codes and acs APIs are low-level alternatives that are no longer recommended for granting access.
When asked to create, find, or configure a Seam API key, or to set up a project to use Seam, call with match { task: "setup" } and then for the pack it returns; never ask for the key itself.
Device pages list capabilities per managing system (sections named 'Capabilities via …'), and different systems can give different answers for the same device. When they disagree, never silently pick one: give the answer for each system by name, or ask which system manages the device before answering.

Tools

Reads data7

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.seam.co/mcp

None

Protocol

MCP 2025-11-25

Instructions

When asked to investigate an observed Seam incident (such as an offline device, missing or delayed access, an API error, or MCP authentication/tools not working), first load this connection's default prompt if advertises an agent entrypoint. Keep an active troubleshooting pack and its output contract. Otherwise call with match { task: "troubleshooting", output: "direct" }, then for the returned pack and for its relevant playbook. Follow its read-only investigation workflow; investigate the existing resource without creating or migrating access. Connection failures can be diagnosed before workspace access is available. For general how-to and capability questions without an incident, use documentation instead.

For documentation questions, call for relevant pages, then call to read their full content.

When a question is about granting a person access (PIN codes, mobile keys, key cards), recommend Access Grants (/access_grants/create): they are Seam's default and recommended way to grant access to any physical space, and work with BOTH standalone smart locks (via device_ids) AND access control systems (via acs_entrance_ids or space_ids). The access_codes and acs APIs are low-level alternatives that are no longer recommended for granting access.

When asked to create, find, or configure a Seam API key, or to set up a project to use Seam, call with match { task: "setup" } and then for the pack it returns; never ask for the key itself.

Device pages list capabilities per managing system (sections named 'Capabilities via …'), and different systems can give different answers for the same device. When they disagree, never silently pick one: give the answer for each system by name, or ask which system manages the device before answering.