Labsco
MCP SERVER

Telnet MCP Server

by PetePeter

Reach router consoles over telnet from an assistant, with an IP allowlist, a command blacklist and an audit trail.

Editors, Terminals & Local Dev Environment
Summary
Console access for an agent, with the guardrails written down.

Telnet on network gear is the definition of a sharp tool. Here the reachable hosts are enumerated at launch rather than chosen at runtime, dangerous commands are blocked by name, and everything that ran is in an audit file afterwards.

What it is

A telnet client for network devices, built for defensive security analysis. The routers it may reach are fixed at launch, several sessions can be open at once, and every command is written to an audit log.

What you get
  • A session opened to an allowed router, with port and connection timeout you can set
  • Commands executed on a connected device, each with its own timeout
  • Sessions closed explicitly
  • Several concurrent router connections
  • A blacklist security model: commands are permitted by default and only dangerous ones are blocked
  • A full audit trail of what ran, written to the path you configure
Requirements

Go 1.21 or later — the binary is built from the repository — and network access to the devices. ROUTER_IPS is the comma-separated list of routers it may reach; LOG_LEVEL and the audit-log path control logging, which defaults to /tmp/telnet-mcp-audit.log.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary