viznoir MCP Server

What the code does

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

    with subprocess.Popen(

        path = os.path.join(output_dir, f"frame_{i:04d}.png")

                    exec(compiled, {"__name__": "__main__"})  # noqa: S102

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

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

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

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

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

This one needs environment variables set before it will start: VIZNOIR_RENDER_BACKEND (Rendering backend: gpu, cpu, or auto), VIZNOIR_OUTPUT_DIR (Output directory for rendered images). The author declared them in the registry entry; get the values from the project itself.