Build with OpenCode. Connect to your devices.
Give OpenCode Seam’s current documentation, then build device integrations from your terminal. Start with the capabilities your application needs and verify them in a sandbox.
Illustrative sandbox workflow with OpenCode: 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 OpenCode.
Add Seam to your project’s OpenCode configuration, check the connection, then let your agent guide the integration.
Connect Seam
With OpenCode installed, merge this entry into opencode.json at your project root. Keep any existing servers and settings.
Sign in with your Seam account using the next command. No Seam API key is needed.
Check the connection
Run this from the same project and complete browser sign-in. Then ask OpenCode to use seam to find the current Access Grants documentation and cite the result.
A successful documentation search confirms that the agent can use the connection.
Set up your application
Paste this into OpenCode. It points to Seam’s setup instructions in /agents.md for your workspace, Seam API key, and your authenticated agent session.
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 OpenCode a concrete task, ask it to check current documentation, and review the result.
Build a guest access service
Reconcile device actions
Check a device before building
Questions.
Client setup references
OpenCode MCP servers ↗OpenCode skills ↗Seam agent setup ↗Seam integration skills ↗Can OpenCode use Seam’s integration skills?
Yes. Run npx skills add seamapi/seam-plugin and select OpenCode in the installer. OpenCode discovers project skills in .opencode/skills/ and .agents/skills/. Ask it to load the relevant Seam skill before implementing the workflow.
Why is the server missing from this project?
Check that the entry is under mcp in the active opencode.json, that its type is remote, and that it is enabled. Run opencode mcp list from the project where you added it.