Skip to main content
Glama
network-terminal-mcp

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.

Persistent raw terminal: open_session(command) takes ssh ..., telnet ..., or serial DEVICE [BAUDRATE]; no shell. Use the same session for commands, pagers, and nested hops. Read startup output; ready only means the local client is running, not that authentication or the network is healthy.

Reads return only new output. If truncated, continue with read_output without an offset. A reader_id on read_output has an independent cursor for already buffered output; it does not collect the transport. Do not re-read history. Use enter=false for single keys. Send secrets only with terminal_write_secret (exactly one of value, env, or file); prefer env or file because value remains in client history.

After sleep or network changes, reopen suspect sessions. A timed-out write may be partial: verify device state before retrying. Close sessions when done. For one-shot SSH use the shell. Before complex work, read network-terminal://usage.

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 persistent terminal: ssh, telnet, or serial DEVICE [BAUDRATE].

No shell is involved. SSH uses the local client, config, agent and keys.

terminal_writeA

Write input, appending a line terminator unless enter=false.

Input is audited after known-secret redaction; use terminal_write_secret for passwords. Timeout fails the session and may mean a partial write.

terminal_readB

Read only new output until quiet or timeout; no prompt shape required.

If truncated, continue with read_output or next_output_offset.

terminal_write_secretA

Send a secret from exactly one source: value, env, or file.

Prefer env or file; plaintext value remains in client history. The server redacts known secrets and never returns or audits the secret value.

read_outputC

Read buffered output from the default or an independent named cursor.

session_statusC

Return state, command, timestamps, idle time, warnings, and exit status.

close_sessionB

Close the terminal and child process, retaining its final status.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
usageFull operating manual: command-based connections, persistent terminal workflow, secrets, and troubleshooting.

TDQS

B3.2/5.0

Scored across 7 tools

Disambiguation4/5

Each tool maps to a distinct operation (open, close, status, write, secret write, read), but terminal_read and read_output both read output and only their descriptions distinguish incremental-vs-buffered semantics. The terminal_read description explicitly redirects to read_output for truncation, which mitigates most of the confusion.

Naming Consistency3/5

Most names follow verb_noun, but the set mixes a 'terminal_' prefix (terminal_write, terminal_read, terminal_write_secret) with unprefixed session verbs (open_session, close_session) and an unprefixed read (read_output). session_status breaks the verb_noun pattern entirely, though all names remain readable and domain-specific.

Tool Count5/5

Seven tools is well-scoped for persistent terminal session management: lifecycle, I/O, secret-safe input, and status each earn a slot with no filler.

Completeness4/5

The session lifecycle (open, write, read, status, close) is fully covered, including a thoughtful secret-handling path. Gaps are minor: no explicit signal/interrupt or resize operation, and no way to enumerate multiple concurrent sessions even though named read cursors are supported.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues