Termix

io.github.sujirodevPublished by GitHub account sujirodevv0.1.0Updated Oct 24, 2026

Manage hosts, snippets, dashboard, metrics and audit of a self-hosted Termix (SSH/RDP/VNC manager)

VerifiedSTDIODesktop onlyCloud & Infrastructure Files & Storage Security & Monitoring

Server details

Identifier: io.github.sujirodev/termix-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 23, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account sujirodev for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.sujirodev%2Ftermix-mcp.svg)](https://sourceweft.com/mcp/io.github.sujirodev%2Ftermix-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant browse and operate a self-hosted Termix SSH/RDP/VNC manager: hosts, snippets, metrics, dashboard, files, and audit trail.

What you can do: Wraps the Termix API through termix-sdk as a curated set of tools rather than a full API mirror. Read tools cover hosts, host metrics and status, dashboard summaries, snippets, audit events and session logs, system info, and API keys. Write tools can create, update, and delete hosts, snippets, credentials, alert rules, tunnels, and files, run snippets and automations, and start, stop, or restart containers. Tools are grouped into toolsets, with hosts, snippets, dashboard, metrics, system, and audit on by default.
When to use it: Use it when you run a self-hosted Termix instance and want an assistant to answer questions about registered hosts, metrics, and audit activity, or to perform routine management such as creating hosts, running snippets, or handling files. Read-only mode suits teams that only want visibility without letting the assistant change anything.
Requirements: Runs locally over stdio via uvx termix-mcp, pip, or the ghcr.io/sujirodev/termix-mcp image. Requires TERMIX_URL pointing at the Termix instance and a Termix API key in TERMIX_API_KEY; JWT and TOTP are not supported. Optional variables control read-only mode, toolsets, tool allow/deny lists, secret redaction, item limits, timeouts, TLS verification, and HTTP transport.

Before you install

The API key in TERMIX_API_KEY carries the permissions of its Termix role, so scope it to the minimum RBAC needed. Write tools can create, update, and delete hosts, snippets, credentials, alert rules, tunnels, and files, and can run snippets and automations on hosts; TERMIX_MCP_READ_ONLY hides and blocks these. Credential tools can reveal stored secrets, and the credentials, files, docker, tunnels, alerts, automations, and users toolsets are opt-in. Admin and dangerous toolsets are excluded…

Installation

In SourceWeft

Open Termix in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

termix-mcp

[CI] [PyPI] [License] [Python] [Docker]

MCP server for Termix, the self-hosted SSH/RDP/VNC manager. Lets an agent (Claude Desktop, Claude Code, Cursor, VS Code...) list and operate your Termix's hosts, snippets, dashboard, metrics and audit trail, built on top of termix-sdk.

Not a 1:1 wrapper of the Termix API: it's a curated set of tools, secure by default (no secrets, no persistent SSH session, no destructive tools outside of explicit toolsets).

[MCP Registry]

Install

Alternatives: pip install termix-mcp or the ghcr.io/sujirodev/termix-mcp image.

Requires a Termix API key (tmx_...) with the minimum RBAC permissions for what the agent will do - see SECURITY.md.

Configure in your client

Claude Desktop / Claude Code (claude_desktop_config.json or .mcp.json):

json

{  "mcpServers": {    "termix": {      "command": "uvx",      "args": ["termix-mcp"],      "env": {        "TERMIX_URL": "https://termix.example.com",        "TERMIX_API_KEY": "tmx_xxxxxxxxxxxxxxxxxxxxxxxx"      }    }  }}

{  "mcpServers": {    "termix": {      "command": "uvx",      "args": ["termix-mcp"],      "env": {        "TERMIX_URL": "https://termix.example.com",        "TERMIX_API_KEY": "tmx_xxxxxxxxxxxxxxxxxxxxxxxx"      }    }  }}

Cursor / VS Code: same format, in each one's MCP configuration file.

Install via the MCP Registry

termix-mcp is published in the official MCP Registry under the name io.github.sujirodev/termix-mcp, with both a PyPI (uvx) package and an OCI (Docker) image listed - see server.json.

Clients that support registry-based discovery can find and install it directly from there instead of hand-writing the JSON config above:

bash

curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.sujirodev/termix-mcp"

curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.sujirodev/termix-mcp"

Then follow your client's own "add from registry" flow, searching for io.github.sujirodev/termix-mcp. You'll still need to set TERMIX_URL and TERMIX_API_KEY yourself - the registry entry doesn't carry your credentials.

You say / what happens

You say	What the tool does
"what hosts do I have registered?"	`termix_list_hosts`
"show me the metrics for host X"	`termix_get_host_metrics`
"run snippet Y on host X"	`termix_run_snippet` (blocked in read-only mode)
"create a new host for this server"	`termix_create_host` (blocked in read-only mode)
"what audit activity happened this week?"	`termix_list_audit_events`

Environment variables

Variable	Default	Description
`TERMIX_URL`	required	Termix base URL
`TERMIX_API_KEY`	required	`tmx_...` API key (JWT/TOTP are not supported)
`TERMIX_SERVICE_URLS`	empty	JSON `{"database": "http://..."}` for installs without a proxy
`TERMIX_VERIFY_SSL`	`true`	Validates the TLS certificate
`TERMIX_TIMEOUT`	`30`	Timeout per request (s)
`TERMIX_MAX_RETRIES`	`2`	Passed through to the SDK
`TERMIX_MCP_READ_ONLY`	`false`	Hides and blocks write tools
`TERMIX_MCP_TOOLSETS`	`default`	`default`, `all`, or a list `hosts,snippets,files`
`TERMIX_MCP_ENABLED_TOOLS`	empty	Allowlist by tool name
`TERMIX_MCP_DISABLED_TOOLS`	empty	Denylist by tool name
`TERMIX_MCP_REDACT_SECRETS`	`true`	Masks secrets in all outputs
`TERMIX_MCP_MAX_ITEMS`	`50`	Default item limit for listings
`TERMIX_MCP_TRANSPORT`	`stdio`	`stdio` or `http`
`TERMIX_MCP_HTTP_HOST` / `_PORT`	`127.0.0.1` / `8765`	HTTP transport bind
`TERMIX_MCP_HTTP_PATH`	generated and logged	Secret path of the HTTP endpoint
`TERMIX_MCP_LOG_LEVEL`	`INFO`	Log level (stderr on stdio, stdout on http)

Toolsets

Enabled by default: hosts, snippets, dashboard, metrics, system, audit.

Opt-in (TERMIX_MCP_TOOLSETS=hosts,files,docker,...): credentials, files, docker, tunnels, alerts, automations, users.

Disabled and explicit (never included in all): admin, dangerous.

TERMIX_MCP_READ_ONLY=true hides and blocks every tool that isn't read-only, in any toolset.

Tools

Full tool list (generated by scripts/generate_tool_docs.py)

Tool	Toolset	Read-only	Destructive	Flags
`termix_get_audit_forwarding`	admin	yes	no	admin
`termix_get_branding`	admin	yes	no	admin
`termix_get_encryption_status`	admin	yes	no	admin
`termix_get_host_defaults`	admin	yes	no	admin
`termix_get_termix_id_status`	admin	yes	no	admin
`termix_list_sso_providers`	admin	yes	no	admin
`termix_update_branding`	admin	no	no	admin
`termix_acknowledge_alert_firing`	alerts	no	no	-
`termix_create_alert_rule`	alerts	no	no	-
`termix_delete_alert_rule`	alerts	no	yes	-
`termix_list_alert_rules`	alerts	yes	no	-
`termix_get_session_log`	audit	yes	no	-
`termix_list_audit_events`	audit	yes	no	-
`termix_list_session_logs`	audit	yes	no	-
`termix_get_automation`	automations	yes	no	-
`termix_list_automations`	automations	yes	no	-
`termix_list_fleets`	automations	yes	no	-
`termix_run_automation`	automations	no	no	data-access
`termix_create_credential`	credentials	no	no	-
`termix_delete_credential`	credentials	no	yes	-
`termix_get_credential`	credentials	yes	no	-
`termix_list_credentials`	credentials	yes	no	-
`termix_reveal_credential`	credentials	yes	no	data-access
`termix_update_credential`	credentials	no	no	-
`termix_get_dashboard_summary`	dashboard	yes	no	-
`termix_get_homepage`	dashboard	yes	no	-
`termix_list_open_tabs`	dashboard	yes	no	-
`termix_list_workspaces`	dashboard	yes	no	-
`termix_get_container`	docker	yes	no	data-access
`termix_get_container_logs`	docker	yes	no	data-access
`termix_get_container_stats`	docker	yes	no	data-access
`termix_list_containers`	docker	yes	no	data-access
`termix_restart_container`	docker	no	no	data-access
`termix_start_container`	docker	no	no	data-access
`termix_stop_container`	docker	no	no	data-access
`termix_create_folder`	files	no	no	data-access
`termix_delete_file`	files	no	yes	data-access
`termix_list_files`	files	yes	no	data-access
`termix_move_file`	files	no	no	data-access
`termix_read_file`	files	yes	no	data-access
`termix_rename_file`	files	no	no	data-access
`termix_write_file`	files	no	no	data-access
`termix_create_host`	hosts	no	no	-
`termix_delete_host`	hosts	no	yes	-
`termix_disable_host_autostart`	hosts	no	no	-
`termix_enable_host_autostart`	hosts	no	no	-
`termix_get_host`	hosts	yes	no	-
`termix_get_network_topology`	hosts	yes	no	-
`termix_list_host_folders`	hosts	yes	no	-
`termix_list_host_tags`	hosts	yes	no	-
`termix_list_hosts`	hosts	yes	no	-
`termix_update_host`	hosts	no	no	-
`termix_get_host_metrics`	metrics	yes	no	-
`termix_get_host_status`	metrics	yes	no	-
`termix_get_metrics_history`	metrics	yes	no	-
`termix_get_proxmox_stats`	metrics	yes	no	-
`termix_list_active_alerts`	metrics	yes	no	-
`termix_list_host_statuses`	metrics	yes	no	-
`termix_create_snippet`	snippets	no	no	-
`termix_delete_snippet`	snippets	no	yes	-
`termix_get_snippet`	snippets	yes	no	-
`termix_list_snippets`	snippets	yes	no	-
`termix_run_snippet`	snippets	no	no	-
`termix_update_snippet`	snippets	no	no	-
`termix_get_preferences`	system	yes	no	-
`termix_get_system_info`	system	yes	no	-
`termix_list_api_keys`	system	yes	no	-
`termix_create_tunnel`	tunnels	no	no	data-access
`termix_delete_tunnel`	tunnels	no	no	data-access
`termix_get_tunnel`	tunnels	yes	no	-
`termix_list_tunnel_presets`	tunnels	yes	no	-
`termix_list_tunnels`	tunnels	yes	no	-
`termix_assign_role`	users	no	no	admin
`termix_get_user`	users	yes	no	admin
`termix_list_credential_access`	users	yes	no	admin
`termix_list_folder_access`	users	yes	no	admin
`termix_list_roles`	users	yes	no	admin
`termix_list_users`	users	yes	no	admin

Total: 78 tools.

Contributing

See CONTRIBUTING.md.

Security

See SECURITY.md for the threat model.

License

MIT

Source: README.md at commit 311eed7

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.0LatestSep 23, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts