write_to_terminalLABSCO SUMMARY
Three tools, and the one that matters is Ctrl+C.
Write and read are the obvious pair. The control character is what makes the loop usable, because anything that can start a long-running process on your machine should also be able to stop one.
What it is
A Node MCP server that drives the Windows command line. Three tools: write to the terminal, read output back, and send a control character such as Ctrl+C.
What you get
- Commands or plain text written to the Windows terminal
- A chosen number of lines of output read back after a command runs
- Control signals sent, including Ctrl+C to stop something already running
- A Windows-native path — it talks to the Windows command line rather than emulating a shell
Requirements
Windows and Node: clone, npm install, npm run build, then point your client at the built index.js. Reading is a separate call from writing — output comes back when you ask for a number of lines, not automatically after a command.
Setup effort
Build from source — clone the repository and build it, then point your client at the built build/index.js
USE CASES
01
Running a command on a Windows box
Send the command, then pull back the lines it printed.
02
Seeing what a command actually printed
Read a set number of lines of output, so a long log comes back in portions rather than all at once.
03
Stopping something that will not finish
Send Ctrl+C to the terminal instead of leaving a process running unattended.
04
Working through a multi-step console task
Alternate writing and reading, and interrupt when a step goes the wrong way.
3 tools
Listed in project docs. Your client may show a different list.
read_terminal_outputsend_control_characterBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. There is no npm package; install by cloning and building.
Requires
node on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Clone the repository and build it, then point your client at the built build/index.js. This one is built from source rather than installed with a single command.
Server setup
Build from source
TERMINAL
git clone https://github.com/capecoma/winterm-mcp.git
cd winterm-mcp
npm install
npm run buildnode
TERMINAL
node <YOUR_PATH_TO_BUILD>/index.jsMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"github.com/capecoma/winterm-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_BUILD>/index.js"
],
"disabled": false,
"autoApprove": []
}
}
}
