Terminal MCP 97208d14

MCPAI代理

提供方 adelie-ai

AI代理 未标注 无需鉴权 社区 / 第三方

terminal-mcp是一个Rust MCP服务器,为MCP客户端(代理、编辑器集成、自动化运行时)提供Shell执行工具。

一句话选型结论

按资料字段整理

Terminal MCP 97208d14 属于AI代理类 MCP 服务器,传输方式未标注,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 5 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量5暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

Shell执行Rust本地部署MCP协议Rust服务器JSON-RPC审计日志

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 5 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 5 个工具,职责相对集中,接入后不容易误操作。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Terminal MCP 97208d14当前 5 未标注 未标注 无 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方adelie-ai上游标注的维护方 adelie-ai
分类AI代理本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

5.6 KB
来自项目仓库与上游目录的原文,未做删改

terminal-mcp

terminal-mcp is a Rust MCP server that exposes shell execution tools to MCP clients (agents, editor integrations, automation runtimes).

Transport

This server speaks the stdio transport, and no other. stdio is the default,
so terminal-mcp serve needs no flag.

The websocket and unix transports are refused. terminal-mcp serve --transport websocket and terminal-mcp serve --transport unix exit non-zero
and print the transport to use instead. Two separate things hold the refusal:

  • Cargo.toml does not enable mcp-core's websocket feature, so no websocket
    listener is compiled into the binary.
  • server_config() in src/lib.rs leaves both transports out of the server's
    transport policy, so mcp-core rejects the request before it opens a socket.

The reason is what the tools do. This server runs arbitrary shell commands as
the user that started it. Neither listener carries authentication in this build,
so a listening socket would give a shell to whoever can reach it. A stdio server
has no socket: the parent process starts it and controls access to it.

terminal-mcp serve --help lists all three transports and shows --host and
--port, because mcp-core gives one CLI to the whole server fleet. Those two
flags belong to the websocket transport and do nothing here.

What the service provides

  • MCP JSON-RPC handling for initialize, initialized, tools/list, tools/call, and shutdown.
  • Built-in execution tool: terminal_execute.
  • Dynamic script tool lifecycle:
    • terminal_store_script
    • terminal_remove_script
    • terminal_list_scripts
    • runtime script_ tools for stored scripts.
  • Structured command results including:
    • exit_code
    • stdout / stderr
    • timed_out
    • stdout_truncated / stderr_truncated.
  • Per-call timeout support and working-directory support (cwd, including ~ expansion).
  • Output tail limiting via max_lines (default 200, 0 = unlimited).
  • Optional audit logging via MCP_TERMINAL_LOG_DIR.

Audit logging (optional)

Set a non-empty MCP_TERMINAL_LOG_DIR to enable logging:```bash
export MCP_TERMINAL_LOG_DIR=/var/log/terminal-mcp
terminal-mcp serve --transport stdio


When enabled:

- Session metadata log: `__session.log`.
- Per-command output log: `__.log`.
- Tool results include `audit_log_file` for command/script executions.

If `MCP_TERMINAL_LOG_DIR` is unset or empty, logging is disabled.

## Logging

Traces, metrics and logs come from `mcp-core`, which installs the subscriber
and holds the guard: this server calls nothing to turn logging on. Full
mechanics (subscriber setup, the metrics facade, span-close events, shutdown
timing) are documented once in the mcp-core
README; this section covers
what is specific to `terminal-mcp`.

### Where it goes

**stderr, always.** The stdio transport frames JSON-RPC on stdout, so a log
line there would corrupt the protocol. This holds at every level, including
`RUST_LOG=trace`.```bash
RUST_LOG=debug terminal-mcp serve --transport stdio

The level contract, and why it matters more here

Level Carries
INFO ids, counts, durations, model names, tool names. Never content.
DEBUG tool arguments, and the reason a tool declined or failed.

This server runs arbitrary shell commands, so its tool arguments are the
highest-value content in the fleet: paths, flags, and sometimes secrets. A
command line, its arguments, its stdout, its stderr, and the working
directory it ran in never reach a span field or an INFO line, at any log
level. RUST_LOG=debug is what it takes to see the assembled tool arguments
(via mcp-core's own dispatch layer, sanitised and size-capped) -- and that is
deliberate, not this server's addition.

What this server emits

mcp-core's dispatch layer already covers the JSON-RPC request and the tool
call: mcp.request and mcp.tools.call spans, and the mcp.requests /
mcp.tools.call / mcp.tools.call.duration metrics, all keyed by method or
tool name, never by argument content.

On top of that, terminal-mcp's own execution path (shared by command,
script, and every stored script_ tool) adds:

  • A terminal.execute span around each spawn, carrying only detach and
    timeout_secs -- never the command line.
  • A terminal.execute counter, labelled outcome: ok, nonzero_exit,
    timeout, detached, or error. A nonzero shell exit is domain
    information mcp-core's own protocol-level outcome cannot see, since the
    JSON-RPC call itself still succeeds.
  • A terminal.execute.duration histogram.

Exporting to a collector

Off by default (otel feature, see Cargo.toml). With it off, no
opentelemetry crate is resolved at all. With it on, configure export with the
standard OTEL_EXPORTER_OTLP_* environment variables -- there are no CLI
flags and no server-specific variables. See the mcp-core
README for
the full variable reference.```bash
cargo build --release --features otel
OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 \
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf \
./target/release/terminal-mcp serve --transport stdio


With no collector configured, the periodic metrics summary still writes to
stderr, so a default-feature install from `cargo install` gets real numbers
in the journal.

## Build and run```bash
cargo build --release
./target/release/terminal-mcp serve --transport stdio

Technical documentation

Detailed technical docs are under docs/README.md:

  • Architecture
  • MCP Protocol and Transports
  • Tool API
  • Audit Logging

Contributor/agent working rules are in AGENTS.md.

Testing```bash

cargo test
```

License

Apache-2.0. See LICENSE-APACHE.

常见问题

5 问
答案由本站依据条目字段整理,不引用上游原文
Terminal MCP 97208d14 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Terminal MCP 97208d14 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Terminal MCP 97208d14 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Terminal MCP 97208d14 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Terminal MCP 97208d14 能提供哪些能力?

资料显示约 5 个工具;能力标签包括 审计日志、Rust、本地部署。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。