A high-performance Rust implementation of a Model Context Protocol (MCP) server for headless terminal [ht](https://github.com/andyk/ht).
A high-performance Rust implementation of a Model Context Protocol (MCP) server for headless terminal ht. That is what the ht mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 6 tools. What each one is for:
ht_create_session — Create new terminal sessionht_send_keys — Send keystrokes to sessionht_take_snapshot — Capture terminal stateht_execute_command — Execute command and get outputht_list_sessions — List all active sessionsht_close_session — Close terminal sessionSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ht MCP's toolset — ht_create_session, ht_send_keys, ht_take_snapshot and 3 more — is a fair guide to whether it matches your workflow. It is maintained by memextech; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Ht MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| ht_create_session | Create new terminal session |
| ht_send_keys | Send keystrokes to session |
| ht_take_snapshot | Capture terminal state |
| ht_execute_command | Execute command and get output |
| ht_list_sessions | List all active sessions |
| ht_close_session | Close terminal session |
For custom installation paths:
```json
{
"mcpServers": {
"ht-mcp": {
"command": "/path/to/ht-mcp",
"args": []
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.