TelnetProxyMCP MCP Server

A Model Context Protocol (MCP) server that provides secure telnet client capabilities for Claude Code and other LLM applications. Designed for defensive security analysis of network devices. That is what the telnetproxymcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• Secure Telnet Client — Connect to router devices with command filtering
• MCP Protocol Support — Full JSON-RPC 2.0 compliance for Claude Code integration
• Security Features — Command filtering, audit logging, session management
• Router Management — Support for multiple concurrent router connections
• Comprehensive Logging — Detailed audit trail for compliance and security

The tools it exposes

The server publishes 7 tools. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server
• Installation — 1. Clone and build: bash git clone cd telnet-mcp-server go mod tidy go build -o telnet-mcp-server
• telnet_connect — The telnet_connect tool exposed by this server
• telnet_execute_command — The telnet_execute_command tool exposed by this server
• telnet_disconnect — The telnet_disconnect tool exposed by this server
• Building — The Building tool exposed by this server
• Testing — The Testing tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: ROUTER_IPS, LOG_LEVEL, AUDIT_LOG_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Go 1.21 or later - Claude Code or compatible MCP client - Network access to target router devices

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. TelnetProxyMCP's toolset — Prerequisites, Installation, telnet_connect and 4 more — is a fair guide to whether it matches your workflow. It is maintained by PetePeter; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.