Up and running in minutes
Install MCPTerminal, connect your agents to a hub, and ship your first work order — this guide covers the full quick-start flow.
Installation
MCPTerminal is a Windows-native application. You need Windows 11 with the .NET 8 runtime. No WSL or container layer required.
Prerequisites
Before you begin, make sure you have:
- Windows 11 (build 22000 or later)
- .NET 8 runtime installed
- An AI agent client — e.g. Claude Code CLI, GitHub Copilot, or any MCP-compatible agent
Download and run
Request early access at claude.konklyn@gmail.com — we'll send you a direct download link. Once you have the package:
# Unzip the release archive, then launch the tray app:
.\run-tray.ps1
# Or start the WinUI shell directly:
MCPTerminal.exe
On first launch, MCPTerminal starts an MCP hub on
localhost:8765 and opens the system-tray icon.
The WinUI window shows all connected terminals and agents.
mcpterminal.http.json. The default
8765 works for single-machine setups.
First Hub
The MCPTerminal hub is the coordination backbone — every agent connects to it and gets access to the full tool library. It runs as a local HTTP server; agents talk to it over loopback.
Verify the hub is running
# Check hub status via the CLI tool:
mcpt hub-status
# Or query the health endpoint directly:
curl http://localhost:8765/health
Connect a second machine (optional)
Peer hubs are supported — each hub registers with the others
using mcpt register-peer. This lets agents on
different machines share terminals and work orders.
# Register a peer hub (replace with the peer's address):
mcpt register-peer --uri http://192.168.1.20:8765
First Agent
Any MCP-compatible agent can connect to your hub. Here's how to wire up Claude Code — the most common setup.
Configure Claude Code
Add the MCPTerminal server to your Claude Code MCP config file
(~/.claude/mcp.json or the project-local equivalent):
{
"mcpServers": {
"mcpterminal": {
"type": "http",
"url": "http://localhost:8765/mcp"
}
}
}
Launch your agent
# Start Claude Code — it auto-connects to the hub on startup:
claude
# The agent should appear in the WinUI terminal list within seconds.
Once connected, your agent has access to every tool in the MCPTerminal library — terminal I/O, file system, work orders, GUI automation, and more.
mcpt list-agents to confirm the agent registered
and to see its assigned terminal ID.
Work Orders CLI
The wo CLI is how you create, assign, and track work
for your agents. Work orders are plain Markdown files in your
workspace — agents read them, execute the task, and mark them
done.
Essential commands
# See your assigned queue:
wo list --mine
# Create a new work order:
wo new "Add login page" --priority P2 --team konklyn
# Show full details for a WO:
wo show MCT-0001
# Advance a WO through the pipeline:
wo move MCT-0001 build --note "starting implementation"
# Mark it done:
wo done MCT-0001 --note "tests green, merged branch wo/MCT-0001"
Pipeline stages
Work orders move through: inbox → build
→ verify → done. Agents pick up WOs
from inbox, do the work, and advance the stage.
Blocked? Use wo block MCT-0001 --reason "...".
Notifications
Each agent role has an inbox file:
notifications/to-coder.md,
to-manager.md, etc. Use
wo notify coder "message" to send a nudge.
Frequently asked questions
Does MCPTerminal work with agents other than Claude?
Yes — any MCP-compatible agent works. GitHub Copilot, Cursor, and custom MCP clients all connect via the hub's HTTP endpoint.
Do my agents need internet access?
The hub itself is fully local. Your agent may call external APIs (OpenAI, GitHub, etc.) depending on its tools, but MCPTerminal never phones home.
How do I update MCPTerminal?
During early access, updates are distributed manually. We'll notify early-access users by email when a new build is ready.
Can I use MCPTerminal with WSL?
You don't need to — MCPTerminal is Windows-native. If you run Linux agents inside WSL, they can still connect to the Windows hub over loopback.
Where can I get help?
Email us at claude.konklyn@gmail.com. During early access we respond to every message.