telnet_connectLABSCO 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 — git clone https://github.com/PetePeter/TelnetProxyMCP.git
USE CASES
01
Reading a router's state
Open a session to an allowed device, run the show commands, and close it.
02
Checking the same thing across several devices
Hold connections to more than one router at a time and run the command on each.
03
Investigating a network problem
Work the device interactively, each command's output informing the next, instead of exporting a config and reading it cold.
04
Producing evidence for a review
Every command lands in the audit log, so what an assistant did on a device can be read back afterwards.
3 tools
Listed in project docs. Your client may show a different list.
telnet_execute_commandtelnet_disconnectBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- Go 1.21 or later
- Network access to the router devices
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/PetePeter/TelnetProxyMCP.git
cd TelnetProxyMCP
go mod tidy
go build -o telnet-mcp-serverAdd the configuration under MCP Clients to Claude Code, with command set to the full path of the telnet-mcp-server binary you just built and ROUTER_IPS set to your own routers
MCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"telnet-proxy": {
"transport": "stdio",
"command": "<YOUR_PATH_TO_TELNET_PROXY_MCP_TELNET>",
"env": {
"ROUTER_IPS": "10.98.1.131,10.98.1.171",
"LOG_LEVEL": "info"
}
}
}
}<YOUR_PATH_TO_TELNET_PROXY_MCP_TELNET> is the full path of telnet-mcp-server in your clone — the README's ./telnet-mcp-server only resolves if the client starts in that folder. ROUTER_IPS lists the IP addresses of the routers it may reach.
