Connect an MCP client

Semwright’s MCP frontend uses the official Rust MCP SDK and stdio. It delegates requests to a broker session; it does not implement an independent desktop execution path.

Start the broker separately

Install a reviewed build first. The MCP process and broker must use the same login user and intended runtime. A client configuration does not start the broker or grant permissions.

A minimal configuration after installing the binaries:

{
  "mcpServers": {
    "semwright": {
      "command": "/home/YOUR_USER/.local/bin/semwright-mcp"
    }
  }
}

Replace the path with the actual installed executable. Client configuration locations and formats vary; use your client’s current instructions rather than copying this into an arbitrary file.

Discover rather than flooding the tool list

The frontend exposes a small discovery and execution surface. Search for a capability, inspect its descriptor, and send a structured request through the gateway. Schemas and risk annotations help a client understand a command; the broker still enforces authorization.

Keep session material private

Explicitly shared session tickets remain sensitive. They do not create new grants or approve dangerous actions. Do not paste tickets, browser debug endpoints or private socket material into prompts. Stdio stdout is reserved for the protocol; human diagnostics belong on stderr.

For fake-backend testing, point the client at the intended fake socket. A fake response is not an observation of your desktop. Remote MCP hosting and automatic task persistence are not implied by this local frontend.

Source: MCP guide and minimal configuration, reviewed 22 September 2026. The source guide contains historical verification wording; current gate evidence is linked from compatibility.