Vessel Browser MCP Server

What the code does

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

const child = spawn(electronPath, [appPath], {

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.

      - name: Update Flatpak manifest
        env:
          VERSION: ${{ steps.tag.outputs.tag }}

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 vessel-browser -- npx -y @quanta-intellect/vessel-browser

{
  "mcpServers": {
    "vessel-browser": {
      "args": [
        "-y",
        "@quanta-intellect/vessel-browser"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.vessel-browser]
command = "npx"
args = ["-y", "@quanta-intellect/vessel-browser"]

{
  "mcpServers": {
    "vessel-browser": {
      "args": [
        "-y",
        "@quanta-intellect/vessel-browser"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "vessel-browser": {
      "args": [
        "-y",
        "@quanta-intellect/vessel-browser"
      ],
      "command": "npx"
    }
  }
}