Termix MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TERMIX_URL | Yes | Your Termix server URL, like http://172.16.20.42:8081 | |
| TERMIX_API_KEY | Yes | Your Termix API key. Keep it only in the config file; do not paste it in a chat. | |
| TERMIX_VERIFY_TLS | No | Set to false only for a self-signed https address | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| termix_healthA | Check that the Termix server is up and the API key works. Calls the health check, then lists hosts to test the key. |
| termix_hostsA | List, read, add, change, or delete Termix hosts. action: list | get | add | update | delete host_id: needed for get, update, delete data: the host fields for add and update (see the README for the field names; run action=list once to see the exact fields your Termix version uses) add and update need confirm=true. delete also needs confirm_phrase="DELETE /host/db/host/". Passwords and keys are hidden in all output. Enter those in the Termix web page. |
| termix_add_many_hostsA | Add several hosts in one go. Each item is the same data you would give to termix_hosts add. Needs confirm=true. Reports each result on its own, so one bad row does not stop the rest. |
| termix_credentialsA | List or read stored credentials. Read-only. Secrets are hidden. action: list | get Use the credential id inside a host's data to link a host to a credential. |
| termix_rolesA | Manage Termix roles, who is in them, and which hosts they can reach. Read actions (run right away): list all roles members users in a role (needs role_id) user_roles roles of one user (needs user_id) users all users, to find a user_id host_access who a host is shared with (needs host_id) folder_access standing share rules for a folder (needs folder) Change actions (need confirm=true, so ask the user first): create needs name (lowercase, digits, _ or -) and display_name update needs role_id, and display_name and/or description assign needs role_id and user_id share_host needs host_id, and role_ids and/or user_ids share_folder needs folder, and role_ids and/or user_ids (also covers hosts added to that folder later) update_access needs host_id, access_id, permission_level and/or duration_hours Destructive actions (need confirm=true and confirm_phrase="METHOD /path"): delete delete a role (needs role_id) unassign take a role off a user (needs role_id and user_id) revoke_access remove a host share (needs host_id and access_id) delete_folder_rule remove a folder share rule (needs access_id) Sharing uses the host's saved credential. No passwords pass through here. |
| termix_callA | Call any other Termix API route. Docs: https://docs.termix.site/api/ method: GET, POST, PUT, PATCH, or DELETE path: like /host/db/host or /health GET runs right away. POST, PUT, PATCH need confirm=true. DELETE needs confirm=true and confirm_phrase="DELETE ". Password and key routes are blocked. Secrets in answers are hidden. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have distinct resource focus, but termix_add_many_hosts overlaps with termix_hosts add, and termix_call can duplicate nearly any other tool. termix_health also overlaps with termix_call GET /health and host listing, though descriptions provide some guidance.
All names use the same termix_ prefix and snake_case, which is predictable. The suffix style is not strictly verb_noun—resources are mostly nouns with actions as parameters—but it remains readable and consistent.
Six tools is well within a reasonable range and covers the domain without excessive fragmentation. The generic escape hatch and batch-add tool each serve a clear purpose.
Core host CRUD, batch host creation, role/access management, credential reads, and health checks are covered. Minor gaps exist—credential writes are intentionally omitted and some operations rely on the generic call tool—but agents have workarounds.