Windows Telnet MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELNET_MCP_PWSH | No | Path to PowerShell 7 executable if it is not in the default location. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| telnet_checkA | Checks whether this machine can open and control a visible Windows Telnet client. |
| telnet_startA | Opens a real, user-visible conhost.exe window running the built-in Windows telnet.exe. If host is supplied, this initiates an outbound Telnet connection. |
| telnet_listB | Lists visible Windows Telnet sessions started by this MCP server process. |
| telnet_statusB | Checks whether a visible Windows Telnet process is still running. |
| telnet_readA | Reads text from the real Windows console screen buffer. Use mode=visible for exactly what the user can see, or mode=tail for recent buffer rows. |
| telnet_sendA | Injects text as real Windows console keyboard events into the visible Telnet session. Set appendEnter=true to submit the line. The text may be transmitted to the remote Telnet server. |
| telnet_keyB | Sends one named key to the visible Telnet console. CTRL+] enters the Microsoft Telnet command prompt. |
| telnet_wait_for_textB | Polls the real console screen until literal text appears or the timeout expires. |
| telnet_focusB | Restores and brings the real conhost.exe Telnet window to the foreground. |
| telnet_closeA | Closes the visible Telnet session. Graceful mode sends CTRL+], then quit. Force mode closes or terminates the process if necessary. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct operation: status/check/list cover different aspects of session state and capability, while read/wait_for_text/send/key separate reading, polling, text injection, and named key injection. There is no meaningful overlap that would confuse an agent.
All tools share a consistent telnet_ prefix followed by a clear verb or verb phrase, such as start, close, send, read, list, and wait_for_text. The naming pattern is uniform and predictable across the entire set.
Ten tools is well-scoped for controlling a visible Windows Telnet client: session lifecycle, I/O, waiting, focusing, and diagnostics are all represented without unnecessary duplication. Each tool contributes a distinct capability.
The toolset covers the full interaction lifecycle: starting a session, connecting, sending input, reading output, waiting for expected text, sending special keys, listing sessions, checking readiness, focusing, and closing. No obvious gap prevents an agent from automating a Telnet workflow.