Trail MCP Server

What the code does

We read the source, 4 d ago · rules ccca72095570

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(cmd, args, { stdio: 'ignore', detached: true })

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 trail -- npx -y usetrail

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

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

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

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

This one needs environment variables set before it will start: TRAIL_API_URL (Only for a self-hosted Trail. Left unset, the connector points at the hosted service.), TRAIL_PROJECT (Overrides the project name, which otherwise comes from the folder you have open.). The author declared them in the registry entry; get the values from the project itself.