Termix runs on your own machine — the client starts it, so there is no endpoint to ping. 106 installs a week from pypi. Last commit 23 Sep 2026.
Manage hosts, snippets, dashboard, metrics and audit of a self-hosted Termix (SSH/RDP/VNC manager)
Today is the operative word: we check Termix every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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 termix-mcp -e 'TERMIX_URL=<TERMIX_URL>' -e 'TERMIX_API_KEY=<TERMIX_API_KEY>' -- uvx termix-mcp
{
"mcpServers": {
"termix-mcp": {
"command": "uvx",
"args": [
"termix-mcp"
],
"env": {
"TERMIX_API_KEY": "<TERMIX_API_KEY>",
"TERMIX_URL": "<TERMIX_URL>"
}
}
}
}
[mcp_servers.termix-mcp]
command = "uvx"
args = ["termix-mcp"]
env = { TERMIX_URL = "<TERMIX_URL>", TERMIX_API_KEY = "<TERMIX_API_KEY>" }
{
"mcpServers": {
"termix-mcp": {
"command": "uvx",
"args": [
"termix-mcp"
],
"env": {
"TERMIX_API_KEY": "<TERMIX_API_KEY>",
"TERMIX_URL": "<TERMIX_URL>"
}
}
}
}
{
"servers": {
"termix-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"termix-mcp"
],
"env": {
"TERMIX_API_KEY": "<TERMIX_API_KEY>",
"TERMIX_URL": "<TERMIX_URL>"
}
}
}
}
Put your own values in place of
<TERMIX_URL> (Base URL of the Termix instance), <TERMIX_API_KEY> (Termix API key (tmx_...)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
TERMIX_MCP_TOOLSETS (default, all, or a comma-separated list (hosts,snippets,files,...)), TERMIX_MCP_READ_ONLY (Hide and block every write tool).
Query OpenTelemetry logs, traces and metrics from a self-hosted OTLP dashboard
Hosts, metrics, Docker and authorized_keys over a macOS terminal's live SSH connections
Manage a self-hosted DNS firewall: block domains, create policies, read query logs and metrics.
Query GreptimeDB metrics, logs and traces with SQL, TQL and RANGE. Manage pipelines and dashboards.
Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).
Self-hosted memory for agent teams. Bi-temporal replay, deterministic retrieval, audit log.
SigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants
MCP server for Dynatrace Managed to access logs, events, and metrics.
Answers built from our own checks of this server.