Skip to content

Connect UseTrawsn through MCP

UseTrawsn’s local MCP server lets Claude Code, Codex, Cursor, and other compatible hosts discover tools for image and video generation, media understanding, and web research. The host launches usetrawsn mcp as a local process and communicates over stdio; media and web requests run through the UseTrawsn service.

The server runs inside the CLI binary and shares its login and model discovery. Install the CLI first, then configure a host below. The MCP tool reference describes the tool surface and read/write boundaries.

Terminal window
usetrawsn mcp --help

If the command is missing, run usetrawsn update.

Store the machine-specific absolute root in Claude’s local project scope:

Terminal window
claude mcp add --scope local usetrawsn -- usetrawsn mcp --allow-root "$PWD"

MCP startup never opens a browser. Existing CLI login is loaded automatically and credentials are refreshed on every tool call.

  1. Call usetrawsn_auth_status.
  2. If unauthenticated, call usetrawsn_login and show its verification URL and user code.
  3. After the human completes login, call usetrawsn_login_poll with the returned session ID.
  4. Call usetrawsn_status to verify the server and account.

Effective local file access is the union of:

  • repeatable --allow-root flags
  • the platform path list in USETRAWSN_MCP_FILE_ROOTS
  • roots advertised by the MCP client
  • the process working directory when no other roots are configured

Canonical checks reject path traversal, sibling-prefix confusion, and symlink escape. Keep roots as narrow as possible. HTTP(S) URLs and existing UseTrawsn upload references do not require local access.

After authentication, ask the host to list the available image models with usetrawsn_list_models, then inspect a selected model with usetrawsn_model_schema. This verifies discovery and shows the inputs before you request generation.

For a first task, ask: “Use UseTrawsn to generate a product image. Check the current image models and the selected model’s schema first.” The host can then use usetrawsn_image_generate. For a local reference image, authorize its directory before asking the host to read or edit it.

See the MCP tool reference for individual tools. Use the CLI reference for operations that the MCP surface does not expose, such as Drive uploads and Page deployments.

Symptom What to check
The host cannot start usetrawsn Run usetrawsn --version in a terminal. If that works, use the executable’s absolute path in the host configuration or restart the host after updating PATH.
mcp is an unknown command Run usetrawsn update, then verify usetrawsn mcp --help again.
Tools are present but authentication fails Call usetrawsn_auth_status and complete the login sequence above. A running server does not by itself confirm account access.
A local image or video is rejected Check that its resolved path is inside an authorized root, including where a symlink points. See local file security.
A wrapper breaks the stdio connection Keep stdout reserved for MCP protocol messages. Send wrapper logs to stderr.