Server Everything vs Smart Terminal
A side-by-side look at the Server Everything 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 Server Everything for other tools and integrations 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 Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
echo, get-annotated-message, get-env.
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 | Other Tools and Integrations | Command Line |
| Quality signal | 73/100 · Great | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 91,512 | 12 |
| Directory activity | 9 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | 17 |
| Full listing | View Server Everything | View Smart Terminal |
Tools & capabilities
Server Everything tools 16
echoEchoes back the input stringget-annotated-messageDemonstrates how annotations can be used to provide metadata about content.get-envReturns all environment variables, helpful for debugging MCP server configurationget-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.get-resource-linksReturns up to ten resource links that reference different types of resourcesget-resource-referenceReturns a resource reference that can be used by MCP clientsget-structured-contentReturns structured content along with an output schema for client data validationget-sumReturns the sum of two numbersget-tiny-imageReturns a tiny MCP logo image.gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.- +4 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.
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Smart Terminal
{
"mcpServers": {
"smart-terminal": {
"command": "npx",
"args": [
"-y",
"smart-terminal-mcp@stable"
]
}
}
}
Frequently asked questions
Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Smart Terminal belongs to Command Line and uses a local stdio subprocess. Pick Server Everything for other tools and integrations 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.
Server Everything is listed as free. Auth: no auth required. 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 modelcontextprotocol-server-everything and smart-terminal as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Server Everything has a quality signal of 73/100 (Great) with 9 views, 0 installs and 91,512 GitHub stars. Smart Terminal has 53/100 (Good) with 2 views, 0 installs and 12 GitHub stars.