Aseprite Live MCP Server

What the code does

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

  local fn, compileErr = load(code, "claude")

    def exec(self, lua: str, *, file: str | None = None, save: bool = False) -> ExecResult:

            proc = subprocess.run(cmd, capture_output=True, text=True, timeout=self.timeout + 30)

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 aseprite-live-mcp -- uvx aseprite-live-mcp

{
  "mcpServers": {
    "aseprite-live-mcp": {
      "args": [
        "aseprite-live-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.aseprite-live-mcp]
command = "uvx"
args = ["aseprite-live-mcp"]

{
  "mcpServers": {
    "aseprite-live-mcp": {
      "args": [
        "aseprite-live-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "aseprite-live-mcp": {
      "args": [
        "aseprite-live-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: ASEPRITE_MCP_BACKEND (live (default) or headless), ASEPRITE_PATH (Path to the Aseprite executable (auto-detected if unset)), ASEPRITE_RELAY_URL (Relay HTTP base for the live backend (default http://127.0.0.1:9878)), ASEPRITE_MCP_NO_UPDATE_CHECK (Set to disable the daily PyPI update check). The author declared them in the registry entry; get the values from the project itself.