Remote Agents vs Smart Terminal
A side-by-side look at the Remote Agents and Smart Terminal MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Smart TerminalCommand Line · Local subprocess (stdio)MCP PTY server providing AI agents with real interactive terminal access53GoodAuth: not declaredVerdict: choose Remote Agents for command line work as a local process; choose Smart Terminal for command line as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Remote Agents when
- You need dedicated capabilities in the Command Line domain.
- You prefer a local stdio subprocess transport.
- You want tools like
exec, read_file, get_info.
SChoose Smart Terminal when
- You need dedicated capabilities in the Command Line domain.
- You prefer a local stdio subprocess transport.
- You want tools like
terminal_start, terminal_exec, terminal_run.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Smart Terminal | |
|---|---|---|
| Category | Command Line | Command Line |
| Quality signal | 56/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 12 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 15 | 17 |
| Full listing | View Remote Agents | View Smart Terminal |
Tools & capabilities
Remote Agents tools 15
execRun a shell command (locally or on a remote agent via `agent_id`)read_fileFile operations (write requires Edit/Bypass)get_infoInspect / change an agent's mode at runtimegit_statusGit operationsschedule_addCron-style tasks on a hosttask_dispatchAutonomous AI tasks run with the host's own credentialssession_listBrowse the host's AI-chat history (claude / opencode / codex / cline / roo / kilo / zed / cursor / gemini / qwen / goose / continue); `session_get` fetches a transcript or a window around one messagesession_searchFull-text search over the host's AI-chat history — a local Tantivy (BM25) index of every provider transcript, returning ranked cited snippets with `session_id` + message position (follow up with `session_get { around_seq }` for the context)list_agentsList agents connected to the relay roomfleet_execRun an operation across the fleet — `target = all \fleet_session_searchSearch the AI-chat history across the whole fleet: every matched host queries its local index, hits merge by score with host labelsfile_searchFind files on a host, and move a file host→host (UDP, SHA-256 verified)- +3 more on the listing page
Smart Terminal tools 17
terminal_startStart a new interactive terminal session.terminal_execExecute a command with deterministic completion detection. Large outputs are truncated to head + tail based on `maxLines`. If the MCP client sends a `progressToken`, long-running calls may also emit best-effort `notifications/progress` updates.terminal_runRun a one-shot non-interactive command using `cmd + args` with `shell=false`. Safer than `terminal_exec` for predictable automation. Output is capped by `maxOutputBytes` rather than head + tail truncation. Shell built-ins such as `dir` or `cd` are not supported. On Windows, `terminal_run` resolves…terminal_writeWrite raw data to a terminal (for interactive programs). Follow with `terminal_read`.terminal_readRead buffered output with idle detection. Large outputs are truncated to head + tail based on `maxLines`. Pass `since` to read incrementally — returns only output emitted after the given byte position.terminal_waitWait for a specific pattern in the output stream. Only output produced **after the call** is matched by default — the echoed command line (which contains any pattern you typed, completion markers included) never triggers a match, including an echo that is still streaming in when the wait starts (wr…terminal_stopStop and clean up a terminal session. Optionally capture a snapshot of recent output or write the full transcript to disk before stopping. On Unix, kills the entire process group to prevent orphan child processes.terminal_listList all active terminal sessions.terminal_extraMeta-tool for discovering and calling extra tools.terminal_send_keySend a named special key.terminal_run_pagedRun a read-only one-shot command using `cmd + args` with `shell=false` and return a single page of stdout lines from the captured output. This pages the returned result instead of using head + tail truncation. Paged mode does not parse partial output, but it can return a concise summary for support…terminal_get_historyRetrieve past terminal output without consuming it. Non-destructive — returns historical output from a rolling buffer (last ~10,000 lines). Useful for reviewing output that was already read or missed.- +5 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Remote Agents
{
"mcpServers": {
"remote-agents": {
"command": "npx",
"args": [
"-y",
"remote-agents"
]
}
}
}
Smart Terminal
{
"mcpServers": {
"smart-terminal": {
"command": "npx",
"args": [
"-y",
"smart-terminal-mcp@stable"
]
}
}
}
Frequently asked questions
Remote Agents is categorized under Command Line and uses a local stdio subprocess. Smart Terminal belongs to Command Line and uses a local stdio subprocess. Pick Remote Agents for command line work and Smart Terminal for command line.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Remote Agents has no declared pricing — check the project's own site. Smart Terminal has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add remote-agents and smart-terminal as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Remote Agents has a quality signal of 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Smart Terminal has 53/100 (Good) with 2 views, 0 installs and 12 GitHub stars.