Build with Hermes Agent. Automate device tasks in your application.
Use Hermes to build workflows with Seam. Connect the current documentation first, then build application logic that records state, handles failures, and verifies each result.
Illustrative sandbox workflow with Hermes Agent: 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 Hermes Agent.
Hermes supports hosted MCP servers through its YAML configuration and discovers their tools when a session starts.
Add the Seam server
Merge this entry into mcp_servers in ~/.hermes/config.yaml. Keep your existing servers and configuration.
Sign in with OAuth in the next step. No Seam API key is needed.
Refresh the connection
Run hermes mcp login seam in a fresh terminal and complete browser sign-in. Then start a new Hermes chat or run /reload-mcp. Ask Hermes to search Seam’s current device-capability documentation and return the source it used.
Prepare your application
Paste the setup prompt into a session with access to your project. It points to /agents.md for instructions on setting up your application’s Seam API key and your delegated agent connection.
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 Hermes Agent a concrete task, ask it to check current documentation, and review the result.
Build a device health report
Make an access workflow repeatable
Document an operational recovery path
Questions.
How do I make new MCP settings take effect?
Start a new session or run /reload-mcp. Hermes reloads the configured connections and refreshes the tools. Verify the change with a documentation request in the session that will use Seam.
Can Hermes reuse Seam’s integration skills?
Yes. For Access Grants, run hermes skills install seamapi/seam-plugin/skills/seam-access-grants. Hermes supports installation from a GitHub skill directory with its supporting files. Confirm the installed skill appears in the active session before starting the integration.