network-terminal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| open_sessionA | Open a raw interactive terminal session and keep it open. Describe the target inline: |
| terminal_writeA | Write exact input to the session's terminal stream. Use this for commands, interactive keystrokes and nested hops such as
|
| terminal_readA | Read terminal output until the stream is quiet or timeout expires. Returns everything received, including pager screens, password prompts, banners and shell output; no prompt shape is required. Use session_status and read_output for offsets and buffered history. |
| terminal_write_secretA | Send a Use this for every secret typed interactively (device logins, ssh, enable, TACACS). The value is resolved inside the server and never appears in tool arguments, results or audit; only the entry name and byte count are logged. |
| read_outputC | Read a bounded slice of accumulated session output by offset. |
| session_statusC | Return state and prompt metadata for an active session. |
| close_sessionC | Close a session and disconnect from the device. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| usage | Full operating manual: raw terminal workflow, nested ssh/telnet hops, secrets, configuration changes, and troubleshooting. |
TDQS
Scored across 7 tools
Most tools have distinct purposes: open/close session, write, write secret, status. The only potential confusion is between terminal_read (live, quiet-based) and read_output (bounded offset slice), but descriptions clarify the difference by pointing to each other.
All names use snake_case and are readable, but conventions are mixed: some follow verb_noun (open_session, close_session, read_output), while others use noun_verb (terminal_write, terminal_read, terminal_write_secret). The 'terminal_' prefix is applied inconsistently.
Seven tools is well-scoped for an interactive terminal session server. Each tool covers a distinct lifecycle operation (open, close, write, read, secret write, status, buffered read) and none feels redundant or excessive.
The set covers the core lifecycle: open, interact, read output, check status, and close. A minor gap is the absence of a list_sessions tool to manage multiple concurrent sessions, but agents can work around this by tracking session IDs themselves.