Skip to main content
Glama
evgenyzh

network-terminal-mcp

by evgenyzh

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
open_sessionA

Open a raw interactive terminal session and keep it open.

Describe the target inline: protocol and port describe the final target, credentials are references (a pass entry, an explicit SSH key file) for ssh/telnet/console. The optional single-hop route is socks (local SOCKS5 proxy) or proxyjump (SSH jump host); use proxyjump to reach a bastion quickly and run further ssh or telnet hops yourself with terminal_write inside the same session. For local console cables use protocol="serial" with an absolute /dev/tty* path in host, serial parameters and allow_serial=true. Every call goes through the client's permission approval gate.

terminal_writeA

Write exact input to the session's terminal stream.

Use this for commands, interactive keystrokes and nested hops such as ssh user@host. enter appends the transport line terminator (newline, or carriage return on serial). The full data string is recorded in the audit; never type passwords, passphrases or other secrets here — use terminal_write_secret.

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 pass entry value at a live password or passphrase prompt.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
usageFull operating manual: raw terminal workflow, nested ssh/telnet hops, secrets, configuration changes, and troubleshooting.

TDQS

B3.4/5.0

Scored across 7 tools

Disambiguation4/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityNo data
ResponsivenessNo issues