Fortress MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

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 r = spawnSync(finder, [cmd], { stdio: ["ignore", "ignore", "ignore"] });

    return os.path.join(root, name)

        self._proc = subprocess.Popen(args, stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)

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 fortress -- uvx tilion

{
  "mcpServers": {
    "fortress": {
      "args": [
        "tilion"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.fortress]
command = "uvx"
args = ["tilion"]

{
  "mcpServers": {
    "fortress": {
      "args": [
        "tilion"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "fortress": {
      "args": [
        "tilion"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: TILION_MCP_PREWARM (Boot the browser at startup so the first tool call is instant (default 1).), TILION_MCP_HEADLESS (Set 0 to show a visible browser window (default 1).), TILION_ALLOW_PRIVATE_EGRESS (Set 1 to allow tools to reach localhost / private IPs (SSRF guard off).), TILION_BASE_URL (Run browsers on a hosted Tilion server instead of locally.), TILION_API_KEY (Bearer key for the hosted Tilion server (cloud mode only).). The author declared them in the registry entry; get the values from the project itself.