pixlcore

I added an MCP server to xyOps: 17 tools for jobs, workflows, alerts, tickets and snapshots The idea is to let an MCP-compatible AI assistant work with the operational data and actions already available in xyOps. For example: find today's failed jobs, inspect their completion details, check alerts on the affected server, then create a ticket summarizing the findings. There are 17 tools covering event/workflow management, job execution and inspection, tickets, alert searches, monitoring snapshots, and connected server listing. A few implementation details for anyone interested: - It runs through `xy mcp stdio` or `xy mcp serve --port 8080`. - Both transports use the same handwritten tool modules, backed by the xyOps SDK. - STDIO uses the CLI's configured API key. HTTP forwards each client's bearer API key to xyOps. - xyOps remains responsible for permissions. You can grant read-and-run access without event editing, or use `--read-only` to disable all writes and job launches. - The docs include Docker setup and a walkthrough with MCP Inspector. Setup and tool reference I'm interested in feedback from people using MCP for operations. Which tasks are you comfortable letting an assistant perform, and which would you keep as read-only investigation?

New in xyCLI v1.2.0: an MCP server for xyOps! Give your AI assistant 17 tools for jobs, workflows, alerts, tickets and monitoring snapshots. STDIO or HTTP, with your existing API permissions. github.com/pixlcore/xycli/blob/main/docs/mcp.md

xyOps users: Please update Node.js for the October security fixes Hi everyone! A quick heads-up: October's Node.js security releases fix several vulnerabilities, including a Brotli decompression flaw that can cause crashes, leak memory, or potentially allow remote code execution. Please update to 22.23.4, 24.22.1, or 26.12.1, or a newer version in your supported release line. The xyOps v1.1.11 Docker image includes patched Node.js 24.22.1. Docker users should deploy the updated image and recreate their containers. The conductor's self-upgrade mechanism only updates xyOps, NOT Node.js. Native installations need a separate Node.js upgrade and service restart. Please check your worker hosts and job environments too. Full details, advisories, and upgrade guidance

xyOps users: Node.js security updates are out, including a fix for potential remote code execution. The v1.1.11 Docker image includes patched Node.js 24.22.1. Conductor self-upgrade does NOT update Node.js. Please upgrade soon. xyops#488

One workflow step failed? Keep the results that worked. New in xyOps v1.1.9: rerun all jobs, freeze successful nodes, or choose which nodes replay saved results. Handy for recovery and testing. xyops#478

New in xyOps 1.1.9: Real terminals, right in your browser Bring interactive troubleshooting into your monitoring workflow. xyOps 1.1.9 adds admin-only PTY terminals for Linux, macOS, and Windows. They use xySat's existing outbound connection, so private servers need no new inbound ports. Read more about it here: xyops#477

I'm excited about this one: xyOps 1.1.9 brings real server terminals to your browser. Run htop, vim, or PowerShell over xySat's existing outbound connection. Linux, macOS, and Windows, with no SSH server needed! xyops#477