Build with Cursor. Bring devices into your app.

Work on your interface and Seam integration in the same editor. Give Cursor the current API references, then connect your application’s existing routes, data models, and tests.

Set up Cursor Troubleshoot an issue

Cursor

Illustrative sandbox workflow

Set up Seam in Cursor.

Use a project configuration to make the same Seam documentation available when you or a teammate opens the repository in Cursor.

01

Add the project connection

Create .cursor/mcp.json in your project, or merge seam into its existing mcpServers object. Use ~/.cursor/mcp.json instead for a personal connection across projects.

.cursor/mcp.json

{
  "mcpServers": {
    "seam": {
      "url": "https://mcp.seam.co/mcp/authenticated"
    }
  }
}

02

Try a documentation lookup

Save the file and restart Cursor. Open Cursor’s MCP settings and authenticate seam in your browser. Then open a new Agent chat and send this prompt. If the tools are missing, check the connection in Cursor’s MCP settings.

Paste into Cursor Agent

Use seam to find the current Connect Webviews documentation. Explain which steps belong in our backend and which belong in our frontend, with source links.

03

Connect your project

Give Cursor the setup prompt with your project open. It can inspect your stack and apply the current Seam setup guidance to the relevant application files.

Seam agent setup

Paste into Cursor Agent

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

Store the application’s Seam API key in its server environment. The OAuth MCP connection does not need it.

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 Cursor a concrete task, ask it to check current documentation, and review the result.

Add account connection to your UI

Agent prompt

Use Seam’s current Connect Webviews documentation to add a device-account connection flow to this app. Reuse our authentication and UI patterns, keep Seam API keys on the server, and show connection status after the user returns.

Extend an existing booking page

Agent prompt

Inspect our booking details page and backend. Add a Seam guest-access section using Access Grants where supported. Show pending, ready, and failed states, and confirm a credential is ready before making it available to the guest.

Review the integration in context

Agent prompt

Review this Seam integration across the frontend, server routes, and tests. Check the current API references and look for exposed Seam API keys, exposed access credentials, or missing action-state handling. Make focused fixes that fit our existing architecture.

Questions.

Client setup references

Cursor MCP setup ↗Cursor skills ↗Seam agent setup ↗Seam integration skills ↗

Should the MCP configuration live in the project?

Project configuration lives in .cursor/mcp.json; personal configuration lives in ~/.cursor/mcp.json. Cursor merges both, with the project entry winning when names match. A shared server URL can live with the repository; each teammate signs in with their own Seam account.

How do I add the Seam skills?

Run npx skills add seamapi/seam-plugin and select Cursor. Project skills can live in .cursor/skills/ or .agents/skills/. Check Customize → Skills to see what Cursor discovered.

Next steps.

Test in a sandbox, then connect your real devices.

Find your device

Get an API key All agent guides

Build with Cursor. Bring devices into your app.

Set up Seam in Cursor.

Add the project connection

Try a documentation lookup

Connect your project

Troubleshoot with your agent.

Connect with Viewer access.

Prompts to try.

Add account connection to your UI

Extend an existing booking page

Review the integration in context

Questions.

Should the MCP configuration live in the project?

How do I add the Seam skills?

Next steps.

Global Infrastructure for Controlling the Physical World