PhyAgentOS-core vs ros-mcp-server
The two are close in size: 2.1k stars for PhyAgentOS-core, 1.4k for ros-mcp-server. Over the days we have tracked them PhyAgentOS-core moved +18.8% and ros-mcp-server +5.7%, so PhyAgentOS-core is growing faster right now.
They split the axes: PhyAgentOS-core leads on noise control and customization and setup ease, ros-mcp-server on model freedom.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Decouples cognition from physical hardware with a session-centered runtime and small target adapters so the same agent codebase runs across sim and real robots.
- Stars
- 2.1k
- Tracked growth
- +18.8%
- Maturity
- ●●●●●
- Last commit
- 4h ago
- Language
- Python
- License
- MIT
- Cost to run
- Free, self-hosted (local compute)
Bridges ROS and the MCP standard to let LLMs fully observe and control robots without modifying robot source code.
- Stars
- 1.4k
- Tracked growth
- +5.7%
- Maturity
- ●●●●●
- Last commit
- 22h ago
- Language
- Python
- License
- Apache-2.0
- Cost to run
- Depends on external model providers; uses your model client / API key.
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | PhyAgentOS-core | ros-mcp-server |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Workspace-wide protocol | ●●●●● Full robot context |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Multi-layer safety | ●●●●● Minimal guidance |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Plugins + YAML configs | ●●●●● Minimal config |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Fully self-hosted | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Specific policy endpoints | ●●●●● Any provider |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Quick CLI onboarding | ●●●●● ROS setup required |
Which one to pick
Pick PhyAgentOS-core if…
Safety-first — built-in multi-layer validation (critic → preflight → target-side SafetyGuard) and auditable file protocols make it suitable for real-robot deployment.
- Noise control: Multi-layer safety (5/5 against 2/5)
- Customization: Plugins + YAML configs (5/5 against 2/5)
- Setup ease: Quick CLI onboarding (4/5 against 2/5)
Pick ros-mcp-server if…
No robot code changes — pick this to add LLM control and observation to an existing ROS system with minimal integration effort and local deployment.
- Model freedom: Any provider (5/5 against 3/5)
What people want from each one
PhyAgentOS/PhyAgentOS-core
robotmcp/ros-mcp-server
Questions people ask
Is PhyAgentOS-core better than ros-mcp-server?
They split the axes: PhyAgentOS-core leads on noise control and customization and setup ease, ros-mcp-server on model freedom. PhyAgentOS-core is worth picking when safety-first — built-in multi-layer validation (critic → preflight → target-side SafetyGuard) and auditable file protocols make it suitable for real-robot deployment.
Which of PhyAgentOS-core and ros-mcp-server keeps my code private?
PhyAgentOS-core: Fully self-hosted (5/5). ros-mcp-server: Self-hostable (4/5).
What does each one cost to run?
PhyAgentOS-core: Free, self-hosted (local compute). ros-mcp-server: Depends on external model providers; uses your model client / API key..
Full profiles: PhyAgentOS/PhyAgentOS-core and robotmcp/ros-mcp-server. Everything else in Robotics & embodied.