Connection testing in progress

SeamUI MCP documentation

Connect an assistant to one SeamUI Workspace, then review any requested action in SeamUI before it runs. Choose your assistant below to follow the right setup steps.

Your SeamUI server URL

Copy this URL into your assistant

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

Connection requests are open on this deployment. Individual assistant sign-in is still being tested. Actions are available.

Never paste provider keys, access tokens, or secrets into a chat.

Choose your assistant

Follow the guide for the product you use. These connections are being tested; a saved connector alone does not mean access is working.

Assistant not listed? Any MCP client that can add a remote server by URL and sign in with OAuth can connect. Follow the steps under Connect below.

Before you connect

You need a Workspace with an active plan or free trial, and an Owner, Admin or User role. Viewer access is not eligible.
If your Workspace is missing or unavailable, check your membership, plan or free trial in the Dashboard, or ask its Owner or Admin to restore eligibility.
Generation also requires the selected provider and feature to be available to your Workspace. Keep provider API keys in SeamUI settings; never paste them into an assistant conversation.

Connect

In your assistant, add the server URL above as a remote MCP server and choose to sign in through SeamUI. Do not add a token, header or provider key.
Review SeamUI's access request and choose one eligible Workspace. To use another Workspace, create a separate connection.
Choose Full access or Read only. With Full access, the assistant creates, updates and generates without another SeamUI confirmation. Your assistant app decides which tool calls it asks you to approve.

What you can do

The capability catalog lists available reads, content actions, image and video generation, references, and status checks. Your connection only permits tools available to your current Workspace access.

The assistant cannot delete SeamUI content or schedule workflows. Crop is not available through this connection. Revoke the connection at any time to stop new actions.

View the capability catalog

Follow finite batch and video recipes

Use your own reference files

The assistant stores a reference image, video or audio file in SeamUI first, then uses it in a generation. There are three ways to give it a file:

A public link: give the assistant a public https URL. SeamUI downloads the file itself, so no setup is needed.
A file already in SeamUI: a generated asset, or a reference you uploaded in the Dashboard. The assistant can find and reuse it directly.
A file on your computer or attached to the chat: the assistant sends it to SeamUI with a short command. This needs an assistant that can run commands and reach www.seamui.com on the internet. Some assistants block unknown sites until you allow the SeamUI domain in their settings, and some cannot send a file to another site at all. The "reference" section of your assistant's guide, linked above, says which applies.

If something goes wrong

If a connection fails, note the visible message and the step where it happened, then contact SeamUI support. Do not send sign-in links, authorization codes, tokens, or keys.

If an action's result is unclear, check its status before trying again: the action may already have started. Keep the operation ID for support.

Manage or revoke access

Open your Workspace in the Dashboard, then the MCP page to review connected assistants and revoke access. Revocation stops future requests but does not cancel generation jobs already started.

Open the Dashboard

Choose your assistant

Follow the guide for the product you use. These connections are being tested; a saved connector alone does not mean access is working.

Assistant not listed? Any MCP client that can add a remote server by URL and sign in with OAuth can connect. Follow the steps under Connect below.

Before you connect

You need a Workspace with an active plan or free trial, and an Owner, Admin or User role. Viewer access is not eligible.

If your Workspace is missing or unavailable, check your membership, plan or free trial in the Dashboard, or ask its Owner or Admin to restore eligibility.

Generation also requires the selected provider and feature to be available to your Workspace. Keep provider API keys in SeamUI settings; never paste them into an assistant conversation.

Connect

In your assistant, add the server URL above as a remote MCP server and choose to sign in through SeamUI. Do not add a token, header or provider key.

Review SeamUI's access request and choose one eligible Workspace. To use another Workspace, create a separate connection.

Choose Full access or Read only. With Full access, the assistant creates, updates and generates without another SeamUI confirmation. Your assistant app decides which tool calls it asks you to approve.

What you can do

The assistant cannot delete SeamUI content or schedule workflows. Crop is not available through this connection. Revoke the connection at any time to stop new actions.

View the capability catalog

Use your own reference files

The assistant stores a reference image, video or audio file in SeamUI first, then uses it in a generation. There are three ways to give it a file:

A public link: give the assistant a public https URL. SeamUI downloads the file itself, so no setup is needed.

A file already in SeamUI: a generated asset, or a reference you uploaded in the Dashboard. The assistant can find and reuse it directly.

A file on your computer or attached to the chat: the assistant sends it to SeamUI with a short command. This needs an assistant that can run commands and reach www.seamui.com on the internet. Some assistants block unknown sites until you allow the SeamUI domain in their settings, and some cannot send a file to another site at all. The "reference" section of your assistant's guide, linked above, says which applies.

If something goes wrong

If a connection fails, note the visible message and the step where it happened, then contact SeamUI support. Do not send sign-in links, authorization codes, tokens, or keys.

If an action's result is unclear, check its status before trying again: the action may already have started. Keep the operation ID for support.