Code with Codex. Build device integrations.

Give Codex Seam’s current documentation alongside your application code. Inspect API schemas, find implementation guides, and build integrations for supported devices.

Set up Codex Troubleshoot an issue

Codex

Illustrative sandbox workflow

Set up Seam in Codex.

With the Codex CLI installed, add the Seam server, sign in, and verify that its tools are available before starting your integration.

01

Add the Seam server.

Run these commands to add Seam to your Codex configuration and complete the browser sign-in.

Codex MCP configuration reference

Run in your terminal

codex mcp add seam --url https://mcp.seam.co/mcp/authenticated
codex mcp login seam

Codex clients on the same host share MCP configuration. You can also configure this endpoint directly in ~/.codex/config.toml or a project’s .codex/config.toml.

02

Verify the connection.

After signing in, start a new Codex session. List your configured servers, then open /mcp inside Codex to check that Seam’s tools are available. Ask Codex to look up an API operation and check that it returns a documentation source.

Check configured servers

codex mcp list

Try: Use Seam to find the parameters for /locks/unlock_door and explain how to check its action result. The configuration listing alone does not prove a tool call succeeded.

03

Start from your project.

Open your application in Codex and paste this prompt. It points Codex to Seam’s setup instructions in /agents.md.

Read the setup guide

Paste into Codex

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

Implement account connection

Agent prompt

Inspect this project, then use Seam’s current Connect Webviews documentation to add an account connection flow. Explain how the application will retrieve devices after a provider account connects.

Handle reservation changes

Agent prompt

Use Seam’s current Access Grants guide to plan guest access in this application. Include credential readiness, changes to the reservation window, and cancellation before implementing the workflow.

Review an integration

Agent prompt

Review this project’s Seam calls against the current API schemas. Check required parameters, error handling, and action-result checks. Identify any device capability assumptions that need verification.

Questions.

Client setup references

Codex MCP configuration ↗OpenAI MCP examples ↗Seam MCP installation ↗

Can I configure Seam without the CLI command?

Yes. In ~/.codex/config.toml, add a [mcp_servers.seam] table with url = "https://mcp.seam.co/mcp/authenticated". Codex also supports project configuration in .codex/config.toml. Run codex mcp login seam, then restart your session and check the loaded server with /mcp.

Can I use the connection in the Codex IDE extension?

Yes. Local Codex clients share MCP configuration on the same host, including the CLI and IDE extension. If you work on a different host or remote development environment, check the MCP configuration loaded in that environment.

What should I check if Seam’s tools are missing?

Run codex mcp list to confirm the configured server, then use /mcp in Codex to inspect active servers. Check the full server URL and the configuration for your current host or project. Ask for a specific Seam documentation lookup to verify a tool call succeeds.

Next steps.

Test in a sandbox, then connect your real devices.

Find your device

Get an API key All agent guides

Code with Codex. Build device integrations.

Set up Seam in Codex.

Add the Seam server.

Verify the connection.

Start from your project.

Troubleshoot with your agent.

Connect with Viewer access.

Prompts to try.

Implement account connection

Handle reservation changes

Review an integration

Questions.

Can I configure Seam without the CLI command?

Can I use the connection in the Codex IDE extension?

What should I check if Seam’s tools are missing?

Next steps.

Global Infrastructure for Controlling the Physical World