CloakBrowser MCP

CloakBrowser MCP se ejecuta en local a partir de un paquete de Node.js publicado en el registro npm: cloakbrowser-mcp, versión 1.14.1. Usa MCP mediante stdio, así que el cliente lo inicia como programa y se comunica con él a través de la entrada y salida estándar. Necesita Node.js; los clientes suelen iniciarlo con npx - el comando habitual es npx -y cloakbrowser-mcp@1.14.1. Lee estas variables de entorno: PLAYWRIGHT_MCP_BROWSER_ENGINE, PLAYWRIGHT_MCP_HEADLESS, PLAYWRIGHT_MCP_OUTPUT_DIR, PLAYWRIGHT_MCP_CODEGEN, PLAYWRIGHT_MCP_SNAPSHOT_BOXES, PLAYWRIGHT_MCP_TIMEOUT_SETTLE, PLAYWRIGHT_MCP_USER_DATA_DIR, CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS, CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS, CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK, CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH y CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS; hay que definirlas en la configuración del cliente para este servidor.

CloakBrowser MCP se ejecuta en local a partir de un paquete de Node.js publicado en el registro npm: cloakbrowser-mcp, versión 1.14.1. El paquete inicia un servidor local que usa MCP mediante Streamable HTTP; después, el cliente se conecta a él por URL. Lee estas variables de entorno: CLOAK_PLAYWRIGHT_MCP_HTTP_HOST, CLOAK_PLAYWRIGHT_MCP_HTTP_PORT, CLOAK_PLAYWRIGHT_MCP_HTTP_ENDPOINT, CLOAK_PLAYWRIGHT_MCP_HTTP_AUTH_TOKEN (secreto), CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_BACKEND, CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_IDLE_TTL_MS, CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_MAX, PLAYWRIGHT_MCP_BROWSER_ENGINE, PLAYWRIGHT_MCP_HEADLESS, PLAYWRIGHT_MCP_OUTPUT_DIR, PLAYWRIGHT_MCP_CODEGEN, PLAYWRIGHT_MCP_SNAPSHOT_BOXES, PLAYWRIGHT_MCP_TIMEOUT_SETTLE, PLAYWRIGHT_MCP_USER_DATA_DIR, CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS, CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS, CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK, CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH y CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS; hay que definirlas en la configuración del cliente para este servidor.

CloakBrowser MCP se ejecuta en local a partir de una imagen de contenedor en un registro OCI como Docker Hub o GitHub Container Registry: ghcr.io/swimmwatch/cloakbrowser-mcp:1.14.1. Usa MCP mediante stdio, así que el cliente lo inicia como programa y se comunica con él a través de la entrada y salida estándar. Necesita Docker u otro entorno de ejecución de contenedores OCI; se inicia con docker run - el comando habitual es docker run -i --rm -e PLAYWRIGHT_MCP_BROWSER_ENGINE -e PLAYWRIGHT_MCP_HEADLESS -e PLAYWRIGHT_MCP_OUTPUT_DIR -e PLAYWRIGHT_MCP_CODEGEN -e PLAYWRIGHT_MCP_SNAPSHOT_BOXES -e PLAYWRIGHT_MCP_TIMEOUT_SETTLE -e PLAYWRIGHT_MCP_USER_DATA_DIR -e CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS -e CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS -e CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK -e CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH -e CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS ghcr.io/swimmwatch/cloakbrowser-mcp:1.14.1. Lee estas variables de entorno: PLAYWRIGHT_MCP_BROWSER_ENGINE, PLAYWRIGHT_MCP_HEADLESS, PLAYWRIGHT_MCP_OUTPUT_DIR, PLAYWRIGHT_MCP_CODEGEN, PLAYWRIGHT_MCP_SNAPSHOT_BOXES, PLAYWRIGHT_MCP_TIMEOUT_SETTLE, PLAYWRIGHT_MCP_USER_DATA_DIR, CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS, CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS, CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK, CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH y CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS; hay que definirlas en la configuración del cliente para este servidor.

CloakBrowser MCP se ejecuta en local a partir de una imagen de contenedor en un registro OCI como Docker Hub o GitHub Container Registry: docker.io/swimmwatch/cloakbrowser-mcp:1.14.1. Usa MCP mediante stdio, así que el cliente lo inicia como programa y se comunica con él a través de la entrada y salida estándar. Necesita Docker u otro entorno de ejecución de contenedores OCI; se inicia con docker run - el comando habitual es docker run -i --rm -e PLAYWRIGHT_MCP_BROWSER_ENGINE -e PLAYWRIGHT_MCP_HEADLESS -e PLAYWRIGHT_MCP_OUTPUT_DIR -e PLAYWRIGHT_MCP_CODEGEN -e PLAYWRIGHT_MCP_SNAPSHOT_BOXES -e PLAYWRIGHT_MCP_TIMEOUT_SETTLE -e PLAYWRIGHT_MCP_USER_DATA_DIR -e CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS -e CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS -e CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK -e CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH -e CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS docker.io/swimmwatch/cloakbrowser-mcp:1.14.1. Lee estas variables de entorno: PLAYWRIGHT_MCP_BROWSER_ENGINE, PLAYWRIGHT_MCP_HEADLESS, PLAYWRIGHT_MCP_OUTPUT_DIR, PLAYWRIGHT_MCP_CODEGEN, PLAYWRIGHT_MCP_SNAPSHOT_BOXES, PLAYWRIGHT_MCP_TIMEOUT_SETTLE, PLAYWRIGHT_MCP_USER_DATA_DIR, CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS, CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS, CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK, CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH y CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS; hay que definirlas en la configuración del cliente para este servidor.

En el formato JSON mcpServers que leen muchos clientes MCP de escritorio y de editores de código, la entrada tiene este aspecto (marcadores de posición entre corchetes angulares):

{
  "mcpServers": {
    "cloakbrowser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cloakbrowser-mcp@1.14.1"
      ],
      "env": {
        "PLAYWRIGHT_MCP_BROWSER_ENGINE": "<valor>",
        "PLAYWRIGHT_MCP_HEADLESS": "<valor>",
        "PLAYWRIGHT_MCP_OUTPUT_DIR": "<valor>",
        "PLAYWRIGHT_MCP_CODEGEN": "<valor>",
        "PLAYWRIGHT_MCP_SNAPSHOT_BOXES": "<valor>",
        "PLAYWRIGHT_MCP_TIMEOUT_SETTLE": "<valor>",
        "PLAYWRIGHT_MCP_USER_DATA_DIR": "<valor>",
        "CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS": "<valor>",
        "CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS": "<valor>",
        "CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK": "<valor>",
        "CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH": "<valor>",
        "CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS": "<valor>"
      }
    }
  }
}

Obtenido de la entrada del registro, sin probar aquí. Lo que hace el servidor, y en qué condiciones, lo determina su editor; conviene revisar su repositorio o sitio web antes de darle acceso a cuentas o archivos propios. Cómo añadir un servidor MCP a un asistente · Antes de conectar