Global-MCP-Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VLADIFF_MCP_PROFILE | Yes | The MCP server profile. Set to 'ops' for this deployment, which exposes operation tools but not publish_prompt. The 'prompt' profile (used by the VLA_Diff workspace instance) includes publish_prompt. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ros_topic_statusA | 查询 ROS 话题状态:采样频率(hz) + 最新消息摘要。 在容器内执行 |
| ros_topic_echoA | 读取 ROS 话题最新 n 条消息(--noarr,不含数组字段内容)。 参数 n 取值范围 1~5。用于查看 /bridge/Instruct、/agent_run/log 等话题内容。 |
| process_statusA | 查询项目关键服务是否在运行(宿主机 pgrep -f 匹配)。 已知服务名: ego_planner / agent_run / tracking_api / tensorrt_api / vlm_detect / roscore;也可以直接传任意进程关键字做匹配。 |
| tmux_statusA | 列出宿主机所有 tmux 会话(名称 / 窗口数 / 创建时间)。 用于确认 sim_bridge / ego-planner / agent_run / fake_prompt 等会话是否存在。 |
| tmux_captureA | 抓取指定 tmux 会话当前 pane 的输出内容(向后 lines 行)。 用于查看某服务在 tmux 中持续输出的日志,如 ego-planner / agent_run 的实时输出。 参数 lines 范围 10~2000。 |
| read_logA | 读取项目日志尾部内容(容器内路径)。 已知服务名: agent_run(run_main/logs/agent_run,自动取最新 process_*.json)、 scene_graph(仓库 log/ 目录,自动取最新文件)。 也可以直接传容器内任意文件路径(如 /home/gwq/workspace/VLA_Diff/log/xxx.json)。 参数 lines 范围 10~2000。 |
| tmux_sendA | 向指定 tmux 会话发送按键/命令。 会话不存在时自动创建 detached 会话再发送。 遵循复用规则:不会 kill-session;需要重启会话内程序时, 先发送 "C-c" 停止旧程序,再发送新启动命令。 |
| restart_serviceA | 重启关键 ROS 服务(先杀进程,再后台启动)。 当前支持: ego_planner(obj_nav.launch)。 安全设计:confirm 必须显式传 True 才执行,防止误杀正在运行的服务。 重启后请调用 ros_topic_status 验证 occupancy 话题有数据才算成功。 |
| exec_cmdA | 在容器内执行任意 shell 命令(通用兜底工具)。 用于 rostopic pub、catkin_make 等临时操作;不经过任何白名单,谨慎使用。 |
| ssh_execA | 在远程主机上执行 shell 命令并返回输出。 host 两种写法(由系统 ssh 解析 ~/.ssh/config):
|
| ssh_hostsA | 列出 ~/.ssh/config 中已配置的主机别名及连接信息。 返回每个 Host 的 别名 / HostName / User / Port / IdentityFile, 用于查询当前哪些机器可用 ssh_exec 直接连。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target distinct layers: ROS topics, host processes, tmux sessions, log files, and remote hosts. Minor overlap exists between process_status and tmux_status for service verification, and tmux_capture/read_log both retrieve output, but their contexts are clearly described.
There is a mix of patterns: tmux_status, tmux_capture, process_status, and ssh_hosts follow object/action style, while read_log, restart_service, and exec_cmd use action/object style. The prefixes help readability, but the inconsistency prevents a higher score.
11 tools is well-scoped for a server covering ROS monitoring, process/log inspection, tmux interaction, command execution, and remote SSH access. Each tool has a distinct operational purpose and none feel redundant.
The server covers the main diagnostic and operational workflows: checking statuses, reading logs, restarting a service, sending tmux commands, and executing shell commands locally or remotely. It lacks a generic service control lifecycle and remote file operations, but exec_cmd and ssh_exec cover many edge cases.