Clipacanvas MCP Server

What the code does

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

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.

        subprocess.run(

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.

    const child = spawn(ffmpegExe, args, { stdio: ['ignore', 'ignore', 'pipe'] });

  el.innerHTML = type === 'busy'

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 clipacanvas -- uvx clipacanvas-mcp

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

[mcp_servers.clipacanvas]
command = "uvx"
args = ["clipacanvas-mcp"]

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

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