Connection testing in progress

Connect OpenClaw

OpenClaw, formerly Clawdbot, can act as an MCP client. This is not Claude or Claude Code.

SeamUI MCP server URL

https://www.seamui.com/api/mcp

Connection requests are open on this deployment. This assistant's sign-in is still being tested.

Copy this deployment's URL. Never put a provider key, OAuth token, or secret in the URL or a chat.

Availability

OpenClaw is still being tested with SeamUI. A saved server entry is not proof that sign-in or a tool call works. Test a safe read before relying on the connection.

Connect OpenClaw

In OpenClaw Control UI, go to Settings > MCP and add a server.
Choose Streamable HTTP and enter the SeamUI MCP server URL above.
Set the server's authentication mode to OAuth (auth: "oauth" in OpenClaw configuration). Do not add a shared bearer token or provider API key.
If using the command line, run openclaw mcp login seamui, then openclaw mcp doctor seamui --probeto test the connection.
Review the connection in SeamUI, then manually choose one Workspace in step 2 and confirm before returning to your client.

Check who can use the connection

OpenClaw uses shared Gateway credentials by default. If several people use one agent, configure per-requester OAuth identity and verify that isolation before connecting SeamUI. Otherwise, use a single-user Gateway: a shared connection could let another sender use your SeamUI permissions.

Use a local file as a reference

OpenClaw sends a local file to SeamUI with a command. Sandboxing is off by default, so commands run on the host and need no network setting. When you turn sandboxing on, local container sandboxes run with no network by default: set agents.defaults.sandbox.docker.network so the command can reach the domain of the server URL above.

If the upload cannot reach SeamUI, give the assistant a public https link to the file, which SeamUI downloads itself, or upload the file in the Dashboard first. Both work with no setting.

If sign-in or the test fails

Note the visible error and contact SeamUI support. Do not paste tokens, authorization codes, or sign-in links into a chat or support request.

Official references

MCP documentation

Connection testing in progress

Connect OpenClaw

OpenClaw, formerly Clawdbot, can act as an MCP client. This is not Claude or Claude Code.

SeamUI MCP server URL

https://www.seamui.com/api/mcp

Connection requests are open on this deployment. This assistant's sign-in is still being tested.

Copy this deployment's URL. Never put a provider key, OAuth token, or secret in the URL or a chat.

Availability

OpenClaw is still being tested with SeamUI. A saved server entry is not proof that sign-in or a tool call works. Test a safe read before relying on the connection.

Connect OpenClaw

In OpenClaw Control UI, go to Settings > MCP and add a server.
Choose Streamable HTTP and enter the SeamUI MCP server URL above.
Set the server's authentication mode to OAuth (auth: "oauth" in OpenClaw configuration). Do not add a shared bearer token or provider API key.
If using the command line, run openclaw mcp login seamui, then openclaw mcp doctor seamui --probeto test the connection.
Review the connection in SeamUI, then manually choose one Workspace in step 2 and confirm before returning to your client.

Check who can use the connection

Use a local file as a reference

If the upload cannot reach SeamUI, give the assistant a public https link to the file, which SeamUI downloads itself, or upload the file in the Dashboard first. Both work with no setting.

If sign-in or the test fails

Note the visible error and contact SeamUI support. Do not paste tokens, authorization codes, or sign-in links into a chat or support request.