Build with Mistral Vibe. Connect your backend to devices.

Use Vibe’s terminal workflow to build Seam into your backend. Connect the current documentation, work in your application’s language, and verify application behavior in a sandbox.

Set up Mistral Vibe Troubleshoot an issue

Mistral Vibe

Illustrative sandbox workflow

Set up Seam in Mistral Vibe.

Use Vibe’s MCP command to add Seam and sign in through your browser without storing a Seam API key.

01

Add Seam to Vibe’s configuration

Run this command and complete the OAuth browser sign-in. Use a current Vibe release with native OAuth support.

Run in your terminal

vibe mcp add seam --url https://mcp.seam.co/mcp/authenticated

02

Inspect the documentation tools

Start a new Vibe session and list the server’s tools. Then ask Vibe to retrieve the current Seam documentation for your application’s language and workflow.

Inside Vibe

/mcp seam

If sign-in is still needed, run /mcp login seam. Check which config.toml is active and whether the project is trusted.

03

Set up the backend integration

Paste the setup prompt with your backend project open. It points to /agents.md for instructions on choosing a workspace and configuring your application’s environment.

Seam agent setup

Paste into Vibe

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

Build a Python integration

Agent prompt

Inspect this Python backend and use Seam’s current documentation to implement a device-listing service. Read the Seam API key from the environment, follow our existing service conventions, and add a sandbox smoke check with clear connection errors.

Connect reservation changes

Agent prompt

Use Seam’s integration guidance to connect this application’s reservation lifecycle to guest access. Compare the available integration approaches with our data model, then implement creation, date changes, and cancellation using the supported approach.

Add a background reconciliation job

Agent prompt

Review our background job patterns and the current Seam action-state documentation. Implement a job that reconciles pending operations, records failures, and avoids retrying completed work. Exercise it with sandbox results and failure fixtures.

Questions.

Client setup references

Vibe MCP servers ↗Vibe configuration ↗Vibe skills ↗Seam agent setup ↗Seam integration skills ↗

Which configuration file should I edit?

Vibe looks for ./.vibe/config.toml before ~/.vibe/config.toml. Project configuration is loaded when the working directory is trusted. Add the server to the active file so a project override does not hide it.

Can Vibe use Seam’s skill files?

Yes. Vibe supports project skill directories under .vibe/skills/ and .agents/skills/. Place the relevant Seam skill directory there with its SKILL.md and supporting files, or use the Seam skills installer when Vibe is offered as a target.

Next steps.

Test in a sandbox, then connect your real devices.

Find your device

Get an API key All agent guides

Build with Mistral Vibe. Connect your backend to devices.

Set up Seam in Mistral Vibe.

Add Seam to Vibe’s configuration

Inspect the documentation tools

Set up the backend integration

Troubleshoot with your agent.

Connect with Viewer access.

Prompts to try.

Build a Python integration

Connect reservation changes

Add a background reconciliation job

Questions.

Which configuration file should I edit?

Can Vibe use Seam’s skill files?

Next steps.

Global Infrastructure for Controlling the Physical World