Build with Cline. Add device controls to your app.

Connect Seam’s current documentation in Cline, then build the integration step by step in your project.

Set up Cline Troubleshoot an issue

Cline

Illustrative sandbox workflow

Set up Seam in Cline.

Use Cline’s Streamable HTTP connection and OAuth sign-in to connect Seam.

01

Add a remote MCP server

Open MCP Servers in the Cline panel and choose Remote Servers. Name it seam, paste this URL, select Streamable HTTP, and choose Add Server. Use the connection’s OAuth authorization control to sign in to Seam.

Server URL

https://mcp.seam.co/mcp/authenticated

For JSON configuration, the transport field is type: streamableHttp. OAuth needs no Seam API key. In the Cline CLI, the cline mcp wizard also offers Authorize OAuth.

02

Verify a documentation request

Check that the server is enabled in MCP settings, then send this to Cline. Review the documentation result before beginning implementation.

Paste into Cline

Use seam to find the current Access Grants documentation. Explain how to create guest access for a specific time window and how to check when the credential is ready. Cite the source.

03

Work through the setup

Use the setup prompt in your project. Follow the human sign-in steps it identifies and let Cline adapt the implementation to your existing code.

Seam agent setup

Paste into Cline

Set up Seam in this project:
fetch https://seam.co/agents.md and follow its instructions.

Choose your workspace permissions.

After 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 guide

Troubleshoot 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 troubleshooting

Authenticated MCP endpoint

https://mcp.seam.co/mcp/authenticated

Try this prompt

Use Seam MCP to investigate why access grant <grant_id>
in workspace <workspace_id> failed at <time and timezone>.
Use the troubleshooting skill pack. Keep the investigation
read-only and explain any missing evidence.

Prompts to try.

Give Cline a concrete task, ask it to check current documentation, and review the result.

Plan guest-access cancellation

Agent prompt

Inspect our booking cancellation flow and use Seam’s current documentation to plan access revocation. Identify the relevant records and API operations, then implement and verify the cancellation path in a sandbox.

Handle device connection failures

Agent prompt

Review this application’s Seam device connection flow. Use the current documentation to distinguish an unconnected account, an offline device, and an unsupported capability. Add useful UI states and tests for each case.

Build a sensor event handler

Agent prompt

Use Seam’s current supported sensor events and webhook verification instructions to build a handler for this project. Handle duplicate deliveries and test the notification logic with fixtures before connecting a real notification destination.

Questions.

Client setup references

Cline MCP setup ↗Cline skills ↗Seam agent setup ↗Seam integration skills ↗

Which remote transport should I select?

Select Streamable HTTP. In a JSON server entry, Cline uses type: streamableHttp. Its documentation says omitting that field selects legacy SSE, so make the transport explicit.

Can I reuse Seam’s skills in Cline?

Yes. Run npx skills add seamapi/seam-plugin and select Cline. Its recommended project location is .cline/skills/. Each skill directory should retain its SKILL.md and supporting files.

What if the server connects but a request fails?

Try a focused documentation search, then inspect the server in Cline’s MCP settings. You can restart an unresponsive connection there.

Next steps.

Test in a sandbox, then connect your real devices.

Find your device

Get an API key All agent guides

Build with Cline. Add device controls to your app.

Set up Seam in Cline.

Add a remote MCP server

Verify a documentation request

Work through the setup

Troubleshoot with your agent.

Connect with Viewer access.

Prompts to try.

Plan guest-access cancellation

Handle device connection failures

Build a sensor event handler

Questions.

Which remote transport should I select?

Can I reuse Seam’s skills in Cline?

What if the server connects but a request fails?

Next steps.

Global Infrastructure for Controlling the Physical World