Wovo MCP Server

What the code does

We read the source, 19 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.

    execSync(`${cmd} "${url}"`, { stdio: "ignore" });

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 wovo -- npx -y @gowovo/wovo

{
  "mcpServers": {
    "wovo": {
      "args": [
        "-y",
        "@gowovo/wovo"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.wovo]
command = "npx"
args = ["-y", "@gowovo/wovo"]

{
  "mcpServers": {
    "wovo": {
      "args": [
        "-y",
        "@gowovo/wovo"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "wovo": {
      "args": [
        "-y",
        "@gowovo/wovo"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: WOVO_TOKEN (Workspace deploy token (wv_…) from wovo.dev settings.), WOVO_WORKSPACE (Target workspace slug (optional; the token resolves a default).). The author declared them in the registry entry; get the values from the project itself.