Skip to content
MCP server

Vytrix

Read-only host activity, history, anomalies and evidence from a Vytrix collector

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, macOS, Linux
Runs
Locally
Version
0.8.0
Listing updated
today

Similar MCP servers

About Vytrix

Vytrix is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

This MCP server is a read-only window onto Vytrix, a system activity monitor for macOS and Linux. Vytrix groups processes by application, shows listening ports tied to their project folders, and tracks Docker and Podman containers, fed by a single-file Python collector with no dependencies. The MCP server lets an assistant query that collector for current activity, history, anomalies and evidence.

It runs from an OCI image over stdio and needs two settings: VYTRIX_URL, the collector's base URL, and VYTRIX_TOKEN, its bearer token, which is read from the environment and never printed. Plain HTTP is accepted only for localhost, and inside a container 127.0.0.1 refers to the container itself, so the URL should be set explicitly.

The collector exposes only reads: snapshot and history endpoints behind a bearer token, plus a health check, and it never kills, signals or changes anything. History is kept in a local SQLite file for 30 days. A native Mac app, a browser dashboard with simulated demo telemetry and an optional read-only Mac cluster view are part of the wider project.

Install

Run in a terminal

claude mcp add vytrix --env VYTRIX_URL='<VYTRIX_URL>' --env VYTRIX_TOKEN='<VYTRIX_TOKEN>' -- docker run -i --rm -e VYTRIX_URL -e VYTRIX_TOKEN ghcr.io/zyvorai/vytrix-mcp:0.8.0

Add to claude_desktop_config.json

{
  "mcpServers": {
    "vytrix": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VYTRIX_URL",
        "-e",
        "VYTRIX_TOKEN",
        "ghcr.io/zyvorai/vytrix-mcp:0.8.0"
      ],
      "env": {
        "VYTRIX_URL": "<VYTRIX_URL>",
        "VYTRIX_TOKEN": "<VYTRIX_TOKEN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "vytrix": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VYTRIX_URL",
        "-e",
        "VYTRIX_TOKEN",
        "ghcr.io/zyvorai/vytrix-mcp:0.8.0"
      ],
      "env": {
        "VYTRIX_URL": "<VYTRIX_URL>",
        "VYTRIX_TOKEN": "<VYTRIX_TOKEN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "vytrix": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VYTRIX_URL",
        "-e",
        "VYTRIX_TOKEN",
        "ghcr.io/zyvorai/vytrix-mcp:0.8.0"
      ],
      "env": {
        "VYTRIX_URL": "<VYTRIX_URL>",
        "VYTRIX_TOKEN": "<VYTRIX_TOKEN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "vytrix": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VYTRIX_URL",
        "-e",
        "VYTRIX_TOKEN",
        "ghcr.io/zyvorai/vytrix-mcp:0.8.0"
      ],
      "env": {
        "VYTRIX_URL": "<VYTRIX_URL>",
        "VYTRIX_TOKEN": "<VYTRIX_TOKEN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "vytrix": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VYTRIX_URL",
        "-e",
        "VYTRIX_TOKEN",
        "ghcr.io/zyvorai/vytrix-mcp:0.8.0"
      ],
      "env": {
        "VYTRIX_URL": "<VYTRIX_URL>",
        "VYTRIX_TOKEN": "<VYTRIX_TOKEN>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • VYTRIX_URLBase URL of the Vytrix collector, e.g. http://host.docker.internal:9847 or https://vytrix.example. Plain HTTP is accepted only for localhost; inside a container 127.0.0.1 is the container itself, so set this explicitly.Required
  • VYTRIX_TOKENBearer token of the collector. Read from the environment only; never printed.Required

What it does

Host activity queries
Ask what a machine is doing right now.
History and anomalies
Review past readings and unusual ranges with evidence.
Read-only by design
The collector never kills, signals or changes anything.
Token authentication
Uses a bearer token read only from the environment.
Container awareness
Underlying collector covers Docker and Podman containers.
30-day history
Local SQLite history with 30-day retention.

Good for

  • Asking which application is using the CPU
  • Finding what is listening on a port and which project owns it
  • Reviewing an anomaly with supporting evidence
  • Checking a remote host without an agent suite

Pricing

Open source

Open source (see repository licence)

Vytrix FAQ

What do I need to run it?

A Vytrix collector, its URL as VYTRIX_URL and its bearer token as VYTRIX_TOKEN.

Can it change anything on the host?

No. The collector is read-only.

Can I use plain HTTP?

Only for localhost.

How long is history kept?

The collector keeps 30 days by default.

Is Vytrix free?

Yes. Vytrix is open source, so you can use and self-host it for free.

How do I add Vytrix to Claude Code?

Run this command in your terminal: claude mcp add vytrix --env VYTRIX_URL='<VYTRIX_URL>' --env VYTRIX_TOKEN='<VYTRIX_TOKEN>' -- docker run -i --rm -e VYTRIX_URL -e VYTRIX_TOKEN ghcr.io/zyvorai/vytrix-mcp:0.8.0

What are the best alternatives to Vytrix?

The closest alternatives to Vytrix are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers