Global-MCP-Server
Provides tools for interacting with ROS topics, including checking topic status, viewing the latest messages, and reading recent topic messages from the configured container.
Provides tools for managing tmux sessions, listing sessions, capturing pane output, and sending commands to sessions, creating them if they do not exist.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Global-MCP-Servercheck ROS topic status and show recent errors from the agent_run log"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Global-MCP-Server
Trae global MCP server (global-diff-ops): the operations tool for the VLA-Diff project (Phase 1 read-only + Phase 2 write operations). This directory is a standalone deployment replica (the source lives in VLA-Diff-MCP/ inside the VLA_Diff repository), registered in Trae's global MCP configuration.
Deployment mode
This deployment runs with VLADIFF_MCP_PROFILE=ops (see the env in the global mcp.json): it exposes 11 operation tools, without publish_prompt. That sensitive write operation (fabricating LLM instructions) is only provided by the MCP instance (vla-diff-prompt, profile=prompt) in the VLA_Diff workspace, so it is not exposed globally. The tool filtering logic is implemented in the _tool decorator in server.py.
Related MCP server: ROS1 Noetic MCP Server
Features
Provide stable tools to the Agent via the MCP protocol, replacing ad-hoc bash commands each time:
Phase 1: read-only tools
Tool | Description | Run location |
| Query ROS topic frequency + latest message | container |
| Read the last n messages of a ROS topic | container |
| Query the status of key service processes | host |
| List tmux sessions | host |
| Capture tmux session pane output | host |
| Read agent_run / scene_graph logs | container |
Phase 2: write tools
Tool | Description | Safety mechanism |
|
| — |
| Send commands to a tmux session (auto-create if it does not exist; no kill-session) | None (uses the reuse rules) |
| Restart ego_planner etc. (kill first, then start; run in the background) | confirm=True explicit confirmation |
| Fallback for arbitrary shell commands inside the container | No whitelist; use with caution |
SSH remote tools
Tool | Description | Safety mechanism |
| Run shell commands on a remote host; host can be a | Password is only passed via environment variable ( |
| List all host aliases and connection information in | Read-only (only reads; no writes) |
Authentication strategy: by default uses ~/.ssh keys (BatchMode; fails immediately with an error instead of hanging). When a password path is provided, code uses password when the source uses password argument when provided. TCP connections to the same host are reused within 10 minutes (ControlMaster), so consecutive commands skip repeated authentication.
Environment Setup
# 创建虚拟环境并按 uv.lock 安装依赖(标准 .venv,已被 .gitignore 忽略)
uv syncRunning
.venv/bin/python server.pyDefault stdio transport; the MCP client (Trae global config ~/.config/Trae CN/User/mcp.json) lifts it as a subprocess.
Prerequisites
The Docker container
ros_noetic_uss_navhas been created (depended on by ROS-type tools).If it is not running, ROS-type tools return a clear error, while tmux / process tools are not affected.
Extension Directions
More restartable services: elastic-tracker, tracking_service, etc. (add as needed to
KNOWN_RESTART).Service configuration: update the start commands to a YAML file to avoid hard-coding them in code.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to interact with ROS2 robotics systems through natural language commands. Supports topic publishing/subscribing, service calls, message analysis, and auto-discovery of ROS2 interfaces for debugging and controlling robots.Mozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with ROS1 Noetic robotic systems by providing tools for topic management, service calls, and parameter configuration. It also supports node inspection, coordinate transform queries, and message introspection via the Model Context Protocol.MIT
- AlicenseAqualityDmaintenanceEnables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.2436MIT
- AlicenseNot gradedqualityBmaintenanceEnables large language models to interact with ROS robots seamlessly, allowing natural language control, real-time sensor monitoring, and autonomous task execution without modifying existing robot code.Apache 2.0
Related MCP Connectors
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Operate smplkit from your agent: feature flags, config, logging, audit, and scheduled jobs.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhywwyzh/Global-MCP-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server