Skylos MCP Server

What the code does

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

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        fixture_result = subprocess.run(

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 proc = spawn(bin, fullArgs, { cwd: root });

    return path.isAbsolute(configured) ? configured : path.join(root, configured);

    result = subprocess.run(

        npmrc = base / ".npmrc"

    return dict(os.environ if environ is None else environ)

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 skylos -- uvx skylos

{
  "mcpServers": {
    "skylos": {
      "args": [
        "skylos"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.skylos]
command = "uvx"
args = ["skylos"]

{
  "mcpServers": {
    "skylos": {
      "args": [
        "skylos"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "skylos": {
      "args": [
        "skylos"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: SKYLOS_API_KEY (Skylos API key for cloud features and MCP authentication). The author declared them in the registry entry; get the values from the project itself.