Developer · Local MCP server
Termix
Manage hosts, snippets, dashboard, metrics and audit of a self-hosted Termix (SSH/RDP/VNC manager)
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sujirodev/termix-mcp- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI, OCI image (Docker)
- Published
- 2026-09-23
- Updated
- 2026-09-23
- Publisher
- sujirodev (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/sujirodev) · how
- Repository
- github.com/sujirodev/termix-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | termix-mcp | 0.1.0 | stdio |
| OCI image (Docker) | ghcr.io/sujirodev/termix-mcp:0.1.0 | - | stdio |
How to connect Termix
Termix runs locally from a Python package published to PyPI: termix-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx termix-mcp. It reads these environment variables: TERMIX_URL (required), TERMIX_API_KEY (required, secret), TERMIX_MCP_TOOLSETS and TERMIX_MCP_READ_ONLY; set them in the client's configuration for this server.
Termix runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/sujirodev/termix-mcp:0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e TERMIX_URL -e TERMIX_API_KEY ghcr.io/sujirodev/termix-mcp:0.1.0. It reads these environment variables: TERMIX_URL (required) and TERMIX_API_KEY (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"termix-mcp": {
"command": "uvx",
"args": [
"termix-mcp"
],
"env": {
"TERMIX_URL": "<value>",
"TERMIX_API_KEY": "<secret>",
"TERMIX_MCP_TOOLSETS": "<value>",
"TERMIX_MCP_READ_ONLY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| TermcpAn MCP server that lets AI agents act like a human at a real terminal, local or over SSH. | Local · HTTP |
| Termdat MCPMCP server for TERMDAT - the terminology database of the Swiss Federal Administration. | Local · stdio |
| Terminal Command Agent by Nova (CIVAI)I run shell commands on your private cloud environment (bash, sh, zsh) | Remote · HTTPLive check: ✓ handshake |
| Terminal MCPMCP server for interactive terminal sessions - SSH, REPLs, database CLIs, TUI apps. | Local · stdio |
| TerrabackScan AWS/Azure/GCP and generate Terraform HCL with import blocks, deterministically, for AI agents. | Local · stdio |
| TerraformGenerate more accurate Terraform and automate workflows for HCP Terraform and Terraform Enterprise. | Local · stdio |
| Terraform Provider Pin LintFinds the.tf lines a clean terraform init is still free to move. | Local · stdio |
| Terraform Registry MCPTerraform providers and modules from the registry. No key required. | Local · stdio |