Register a new Schema Cloud Connector in the SmartThings Developer Center (not the legacy Developer Workspace, which ended Schema support in August 2025), providing a webhook URL and OAuth 2.0 client credentials
Implement the webhook endpoint to handle the five interaction types: discoveryRequest, stateRefreshRequest, commandRequest, grantCallbackAccess, and integrationDeleted
In the discoveryRequest handler, return a device list payload describing each device with its externalDeviceId, friendlyName, deviceHandlerType, and manufacturerInfo
In stateRefreshRequest, query your cloud for current device state and return the mapped SmartThings capability attributes (e.g., switch: on/off, level: 0-100)
In commandRequest, translate SmartThings capability commands into your cloud's API calls, then return the updated state
Test the integration in the SmartThings mobile app by linking the account; verify devices appear and commands round-trip correctly
Known gotchas
SmartThings Schema moved from Developer Workspace to the Developer Center (console.smartthings.com) in August 2025; new connectors must be registered in the new location
The OAuth token exchange (grantCallbackAccess) must complete within a short window; delays or misconfigured redirect URIs cause the linking flow to silently fail
SmartThings may retry webhook calls on timeout; make interaction handlers idempotent to avoid duplicate commands being sent to your cloud
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp