Termix

io.github.sujirodev由 GitHub 帳號 sujirodev 發布v0.1.0更新於 Oct 24, 2026

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

已驗證STDIO僅桌面雲端與基礎設施檔案與儲存安全與監控

服務詳細資訊

識別碼: io.github.sujirodev/termix-mcp
傳輸: STDIO
執行環境: Desktop only
信任: Verified
發布於: Sep 23, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 sujirodev。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![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)

概覽

AI 產生的概覽

讓助理瀏覽與操作自架的 Termix（SSH/RDP/VNC 管理器）：主機、程式碼片段、指標、儀表板、檔案與稽核記錄。

可以做什麼: 以 termix-sdk 封裝 Termix API，提供精選的工具集，而非完整 API 對映。讀取類工具涵蓋主機、主機指標與狀態、儀表板摘要、程式碼片段、稽核事件與工作階段記錄、系統資訊以及 API 金鑰。寫入類工具可建立、更新與刪除主機、程式碼片段、認證資料、告警規則、通道與檔案，執行程式碼片段與自動化，並啟動、停止或重啟容器。工具依工具集分組，預設啟用 hosts、snippets、dashboard、metrics、system 與 audit。
適用情境: 當你自架 Termix 執行個體，並希望助理回答已註冊主機、指標與稽核活動相關問題，或執行建立主機、執行程式碼片段、處理檔案等日常管理作業時適用。唯讀模式適合只想要可視性、不允許助理做任何變更的團隊。
執行需求: 透過 uvx termix-mcp、pip 或 ghcr.io/sujirodev/termix-mcp 映像以 stdio 在本機執行。需要 TERMIX_URL 指向 Termix 執行個體，並在 TERMIX_API_KEY 中提供 Termix API 金鑰；不支援 JWT 與 TOTP。選用變數可控制唯讀模式、工具集、工具允許/拒絕清單、機密遮蔽、項目上限、逾時、TLS 驗證與 HTTP 傳輸。

安裝前請注意

TERMIX_API_KEY 中的 API 金鑰具有其 Termix 角色的權限，應依最小 RBAC 授權。寫入類工具可建立、更新與刪除主機、程式碼片段、認證資料、告警規則、通道與檔案，並可在主機上執行程式碼片段與自動化；TERMIX_MCP_READ_ONLY 會隱藏並封鎖這些工具。認證資料類工具可顯示已儲存的機密，credentials、files、docker、tunnels、alerts、automations 與 users 工具集需明確啟用。admin 與 dangerous 工具集不包含在 all 中。

安裝

在 SourceWeft 中

開啟儀表板中的 Termix，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照儲存庫中的啟動說明。

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

來源：README.md，提交 311eed7

工具

SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

v0.1.0最新Sep 23, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。
已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。
已列出工具15 分
請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。
描述必需15 分
圖示10 分
文件15 分
授權條款10 分