Swebsy MCP Server

What the code does

We read the source, 2 h 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 kindDir = path.join(base, kind);

  const child = spawn(process.execPath, [entry, "--broker"], {

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 mcp -- npx -y @swebsy/mcp

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@swebsy/mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp]
command = "npx"
args = ["-y", "@swebsy/mcp"]

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@swebsy/mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@swebsy/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SWEBSY_AGENT_PORT (Port the local relay listens on (default 37373)), SWEBSY_AGENT_DIR (Where screenshots and exports land (default: .swebsy-agent in the workspace)), SWEBSY_APP_URL (Studio origin used for the pairing link (default https://studio.swebsy.com; set this for local or self-hosted Studio)), SWEBSY_NO_OPEN (Set to skip auto-opening the pairing link in the browser). The author declared them in the registry entry; get the values from the project itself.