ONT MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONT_HOST | No | ONT IP address, e.g. `192.168.1.1` | |
| ONT_PORT | No | SSH port | 22 |
| ONT_USER | No | SSH username | admin |
| ONT_LABEL | No | Friendly name shown in approval dialogs | Fibre ONT |
| ONT_CONFIG | No | Path to a JSON config file for multiple ONTs | |
| ONT_PROMPT | No | Regex for the CLI prompt, only if yours is unusual | > or # |
| ONT_KEYCHAIN | No | Keychain (macOS) / Secret Service (Linux) entry name | |
| ONT_PASSWORD | No | The password itself (easiest, least safe) | |
| ONT_READ_ONLY | No | `1` turns off all changes | |
| ONT_PASSWORD_FILE | No | Path to a file holding only the password |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ont_showA | Read status or settings from the fibre ONT with 'show '. Read-only, safe. Common items: status (uptime, firmware, WAN), wan, interface, lan, dhcp, arp, route, remoteaccess, portforward, tr069. Call ont_help with path 'show' to list every item this ONT offers. |
| ont_helpA | Ask the ONT's own CLI what commands exist under a path: '' for the top level, 'show', 'config', 'config wan' and so on. Read-only: it only appends '?'. Use it to explore before running a change. |
| ont_runA | Run a command that changes the ONT (config ..., save, reboot, ...). Before it runs, the person at the computer sees a dialog naming the ONT, the command and its risk, and must type a confirmation word; you cannot answer it. High-impact commands (reboot, reset, restore, firmware, WAN/LAN/PPP/VLAN, accounts, remote access) need that word typed. Explain in 'reason' why the change is needed. Many ONTs need a save command (for example 'config save') before a change survives a reboot. |
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 3 tools
The three tools split cleanly along read / discover / write lines: ont_show reads values, ont_help enumerates the CLI tree read-only, and ont_run executes changes behind a confirmation dialog. An agent can pick correctly from the verb alone, and the descriptions reinforce the boundary by naming the safety semantics of each.
All three follow the same ont_<verb> pattern (ont_show, ont_help, ont_run) with lowercase snake-style and a single shared namespace prefix. No mixed conventions or stray casing.
Three tools is on the lean side, but for a generic CLI passthrough this is the right shape: one read path, one discovery path, one mutation path, with domain breadth handled by arguments rather than tool proliferation. Slightly under-scoped only if one expected dedicated helpers for common tasks like save or status.
Read, explore, and mutate are all covered, including a confirmation flow and guidance about needing 'config save' after changes. Minor gaps: no structured/parsed output contract, no dedicated save or reboot convenience tool, and no session/logout or firmware-upload handling, though all are reachable via ont_run.