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 分