VEO 3.1 MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        full_path = os.path.join(self.out_dir, f"{filename}.{self.config.default_image_format}")

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 veo-mcp-server -- uvx veo-mcp-server

{
  "mcpServers": {
    "veo-mcp-server": {
      "command": "uvx",
      "args": [
        "veo-mcp-server"
      ]
    }
  }
}

[mcp_servers.veo-mcp-server]
command = "uvx"
args = ["veo-mcp-server"]

{
  "mcpServers": {
    "veo-mcp-server": {
      "command": "uvx",
      "args": [
        "veo-mcp-server"
      ]
    }
  }
}

{
  "servers": {
    "veo-mcp-server": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "veo-mcp-server"
      ]
    }
  }
}