Tourwright MCP Server

What the code does

We read the source, 19 h ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

2.5.0 → 2.6.0: import { mkdirSync, mkdtempSync, readdirSync, rmSync } from 'node:fs'

    const child = spawn(process.execPath, [RUN_JOB, input, output, JSON.stringify(options)], { stdio: ['ignore', 'pipe', 'inherit'] })

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      const child = spawn(line, { shell: true, stdio: ['pipe', 'ignore', 'pipe'] })

import { mkdirSync, mkdtempSync, readdirSync, rmSync } from 'node:fs'

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add tourwright -- npx -y tourwright

{
  "mcpServers": {
    "tourwright": {
      "command": "npx",
      "args": [
        "-y",
        "tourwright"
      ]
    }
  }
}

[mcp_servers.tourwright]
command = "npx"
args = ["-y", "tourwright"]

{
  "mcpServers": {
    "tourwright": {
      "command": "npx",
      "args": [
        "-y",
        "tourwright"
      ]
    }
  }
}

{
  "servers": {
    "tourwright": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "tourwright"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: TOURWRIGHT_API_URL (Send jobs to a Tourwright API instead of rendering on this machine), TOURWRIGHT_API_TOKEN (Token for TOURWRIGHT_API_URL).