Connection testing in progress

Connect Cursor

Use this guide for the Cursor editor and the Cursor CLI. Both read the same MCP configuration.

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

Cursor has been tested with SeamUI. Adding the server is only the first step; verify a safe read from your selected Workspace before relying on the connection.

Before you start

You need Cursor, an eligible SeamUI Workspace (active plan or free trial), and an Owner, Admin or User role. You do not need a client ID, secret, header, or provider API key in the configuration below.

Connect Cursor

Copy the SeamUI server URL above and add it to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json at the root of one project:

{
  "mcpServers": {
    "seamui": {
      "url": "YOUR_SEAMUI_MCP_URL"
    }
  }
}

Replace the URL placeholder with the copied address. Do not add an auth block, a header, or a token.
In the editor, open Customize in the sidebar and start sign-in for the seamui server. In the CLI, run agent mcp login seamui.
Sign in to SeamUI, review the connection, then manually choose one Workspace in step 2 and confirm before returning to Cursor.
Check that the server is enabled (agent mcp list in the CLI), then ask the agent for a safe read of the selected Workspace before any write.

Use a local file as a reference

Cursor sends a local file to SeamUI with a command the agent runs in your terminal. When that command runs in the Cursor sandbox, network access is restricted: approve the command when Cursor asks to run it outside the sandbox, or add the SeamUI domain to the network allowlist in ~/.cursor/sandbox.json or .cursor/sandbox.json.

If the upload cannot reach SeamUI, give the agent 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 does not finish

Check that the URL is the same one shown above, then read the MCP logs from the Output panel (select MCP Logs). If it still fails, note the message and contact SeamUI support. Never share tokens, authorization codes, or the query string of a callback URL.

Official references

MCP documentation

Connection testing in progress

Connect Cursor

Use this guide for the Cursor editor and the Cursor CLI. Both read the same MCP configuration.

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

Cursor has been tested with SeamUI. Adding the server is only the first step; verify a safe read from your selected Workspace before relying on the connection.

Before you start

Connect Cursor

Copy the SeamUI server URL above and add it to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json at the root of one project:

{
  "mcpServers": {
    "seamui": {
      "url": "YOUR_SEAMUI_MCP_URL"
    }
  }
}

Replace the URL placeholder with the copied address. Do not add an auth block, a header, or a token.
In the editor, open Customize in the sidebar and start sign-in for the seamui server. In the CLI, run agent mcp login seamui.
Sign in to SeamUI, review the connection, then manually choose one Workspace in step 2 and confirm before returning to Cursor.
Check that the server is enabled (agent mcp list in the CLI), then ask the agent for a safe read of the selected Workspace before any write.

Use a local file as a reference

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