# Seam setup for coding agents

Seam gives your application an API for supported smart locks, access systems,
thermostats and sensors. Start with the user's job and the exact device model,
account, region and capabilities. A catalog entry does not imply that every
operation is available.

## 1. Get the current implementation guidance

Connect the public documentation MCP server:

    https://mcp.seam.co/mcp

It requires no account. Its tools are `search_docs`, `get_docs`, `search_api`,
`get_apis`, `search_prompts`, `get_prompt` and `get_prompt_context`.

Use `search_api` to find the relevant operation and `get_apis` to inspect its
current parameters and response. Use `search_docs` and `get_docs` for prerequisites
and provider limits. Use `search_prompts`, then `get_prompt` and
`get_prompt_context`, to load a reference implementation matching the project's
framework and integration mode. Follow the names and paths returned by the server.

The public endpoint provides documentation and guidance. It does not execute
workspace API calls.

- MCP installation: https://www.seam.co/docs/api/mcp-installation
- Integration plugin: https://github.com/seamapi/seam-plugin
- Supported devices: https://www.seam.co/supported-devices-and-systems

## 2. Set up a workspace and credential

Start here: https://console.seam.co/signup

Use a sandbox for simulated integration tests. Before controlling real hardware,
confirm the intended production workspace, account, device and authorized action.
Sandbox results do not establish physical-device behavior.

For the maintained setup workflow, call `get_prompt` with `project_setup`, then
load its supporting paths with `get_prompt_context`. It covers the human's CLI
wizard or Console bootstrap and the agent's separate delegated access.

The CLI package is `@seamapi/cli`. The application's JavaScript SDK package is
`seam`. They serve different purposes.

The human can install the CLI and run the wizard in their own terminal:

    npm install --global @seamapi/cli
    seam wizard

Console fallback: https://console.seam.co/dashboard/wizard

Keep `SEAM_API_KEY` in the application's environment or secret manager. Never put
its value in a conversation, source code, log or MCP client configuration. Keep
local environment files out of version control.

## 3. Choose the execution path

For an agent's delegated session, use the separate authenticated MCP endpoint:

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

Follow `project_setup` and the MCP client's configuration instructions. Complete
the sign-in and permission flow, then inspect the tools actually exposed to that
session. The maintained runtime uses `api_request` for authorized API requests;
do not assume an anonymous docs connection can execute them.

For application code, use the current Seam SDK and the environment credential.
For CLI work, inspect `seam --help` and the selected operation's help. Verify the
workspace with a read before making an authorized change. An empty device list
can mean the intended provider account has not been connected yet.

Connect Webviews: https://www.seam.co/docs/core-concepts/connect-webviews

## 4. Build and verify the user's workflow

- Guest access: use Access Grants to define the person, doors and time window.
  Confirm the credential is ready before sharing it. Test changes and cancellation.
  https://www.seam.co/docs/use-cases/granting-access
- Climate: check the actual device's HVAC mode capabilities and set-point limits.
  Track the action and read current settings again. A set point is not the measured
  room temperature.
  https://www.seam.co/docs/capability-guides/thermostats
- Sensors: check supported events, verify the webhook signature and handle duplicate
  deliveries. Your application owns routing and the notification destination.
  https://www.seam.co/docs/capability-guides/noise-sensors

A request accepted by an API is not proof that the physical operation completed.
Check the documented action result or required state readback. Preserve failures,
reconcile state before retrying and clean up resources created for a test.

- Device capabilities: https://www.seam.co/docs/core-concepts/devices/index
- Action attempts: https://www.seam.co/docs/core-concepts/action-attempts
- Documentation: https://www.seam.co/docs
- Support: support@seam.co