Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Give your agent a body: observe and control simulated robots (LIBERO, RoboDojo) over MCP.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"embodify": {
"command": "uvx",
"args": [
"embodify-mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add embodify -- uvx embodify-mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"embodify": {
"command": "uvx",
"args": [
"embodify-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"embodify": {
"type": "stdio",
"command": "uvx",
"args": [
"embodify-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub YidaYang, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.0a2) llegó al registro hace 35 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, HotCodePush
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Embodify
Give your agent a body.
Your best embodied agent is your favorite agent.
Embodify lets the agent you use every day — Claude Code, Codex or any other MCP-capable agent — see and control robots directly, and keeps everything else that makes it yours. Bring in frontier models with embodied manipulation skills, such as GPT-6 Astra and Claude Opus 5.5, and let your AI companion step into the physical world.
中文 · One-line setup · Backends · For research · Skills · Roadmap
First release (0.1.0a1). Supports LIBERO and RoboDojo today; support for
RoboTwin and the LeRobot SO-101 arm is coming soon.
Most embodied agents are built from scratch: a dedicated harness wraps a model, hands it a fixed set of robot actions, and nothing else. The agent you use every day already has what those harnesses lack:
Embodify keeps all of that and adds a body. Install the plugin and your agent gets robot observation and control tools over MCP — a protocol it already uses for everything else — plus skills that teach it how to operate robots and how to achieve recursive self-improvement (RSI) from its own experience.
A general agent with a body is stronger than a harness that can only move a robot:
Embodify is an agent plugin with two parts, and installing the plugin gives your agent both:
| Part | What it gives your agent |
|---|---|
MCP server (embodify-mcp, registered as embodify) | Tools to list tasks, start an episode, observe cameras and robot state, move end effectors, open and close grippers, and coordinate two arms. |
| Skills | Know-how: running a careful observe–act loop, keeping a profile of the robot body and cameras, and learning from past episodes. More perception skills are coming soon. |
flowchart LR
A["Your agent Claude Code · Codex · …"] -- "MCP (stdio)" --> B["embodify-mcp episodes · budgets · logs"] K["Embodify skills"] -. "loaded by" .-> A B --> I["Backend interface"] I --> L["LIBERO"] I --> R["RoboDojo"] I --> T["RoboTwin (WIP)"] I --> H["SO-101 and other real robots (WIP)"] I -. "SSH / TCP" .-> G["Remote server"]
The MCP server is the front end. Each simulator, benchmark or robot is a backend behind one small interface, so adding a new one does not change what the agent sees. Highlights:
reset_task reconnects.| Backend | Robot | Status |
|---|---|---|
fake, fake-two-arm | Kinematic diagnostic, one or two arms | ✅ Included, no simulator needed |
libero | Franka Panda, 130 tasks in 5 suites | ✅ Included |
robodojo | Dual ARX X5, all 54 simulation tasks | ✅ Included |
| RoboTwin | Dual-arm manipulation benchmark | 🚧 Coming soon |
| LeRobot SO-101 | Real robot: 5-DoF arm with gripper | 🚧 Coming soon |
remote | Any backend above, on another machine | ✅ SSH or trusted TCP |
Coming soon: robot arms such as xArm, mobile manipulators, humanoids and dexterous hands. If there is a simulator or robot you would like us to support, open a GitHub issue with details about it. We welcome contributions of new backends.
Embodify doubles as a testbed for the embodied manipulation abilities of language models and agent frameworks. Run GPT, Claude, Gemini, Qwen and other models, through Claude Code, Codex or your own agent framework, on the same simulated benchmarks with the same tools, and compare them directly.
--lock-task fixes the scene.Typical studies include zero-shot robot manipulation by frontier models, comparisons of agent frameworks on the same model, the effect of skills and memory, and recursive self-improvement across episodes. See citation for how to cite Embodify and what to report.
Paste this into Claude Code, Codex or any other agent you use:
Install Embodify (https://github.com/YidaYang/embodify) for yourself, then set up a LIBERO environment or connect to my existing simulator.
That's it. Your agent installs the Embodify plugin, sets up the simulator and tells you when to restart the session. (Agents: follow the agent setup guide.)
Embodify starts its MCP server with uv, straight from PyPI. If you do not have uv yet, install it with python -m pip install uv or the official installer.
claude plugin marketplace add YidaYang/embodify
claude plugin install embodify@embodify
codex plugin marketplace add YidaYang/embodify
codex plugin add embodify@embodify
The plugin brings both the MCP server, registered as embodify, and the skills. The server starts on the Fake backend, so you can try the tools right away; connect a real simulator next. It reads its settings from ~/.embodify/config.json (see backend setup). To check the package on its own, without an agent:
uvx --from embodify-mcp embodify-mcp-smoke # end-to-end check: no simulator, GPU or model needed
SKILL.md folders), copy or link the folders in plugin/skills/ into its skills directory.Restart the session, then ask your agent something like *"Reset the task, describe what the cameras show, then raise the gripper 5 cm."*
Let your agent do this step. Paste:
Connect Embodify to a real simulator for me: set up LIBERO on this machine, or connect to my existing simulator. Follow https://github.com/YidaYang/embodify/blob/main/docs/agent-setup.md.
Your agent installs the simulator or connects to yours over SSH, writes the server settings to ~/.embodify/config.json and asks you to restart the session. To do it by hand, see backend setup.
Add "monitor-port": 8765 to ~/.embodify/config.json and open http://127.0.0.1:8765 to watch the robot work live, with every camera view, the robot state and each tool call your agent makes, or to replay any past episode frame by frame. To browse saved runs without a running server:
uvx --from embodify-mcp embodify-mcp-monitor # reads ~/.embodify/runs
The monitor listens on localhost only.
| Tool | Purpose |
|---|---|
get_session_info | Current run, task, step budget and robot state; no images |
list_tasks | Browse the backend's task catalogue |
reset_task | Start an episode and return the first camera images |
observe | Camera images and robot state, without moving |
move_relative | Move one end effector by a translation and optional rotation |
set_gripper | Open or close a gripper |
control_arms | Move several arms together with common progress (two-arm backends) |
stop_episode | End the episode and write its record |
Translations are in meters, rotations in radians, quaternions in xyzw order. Frames and stop reasons are defined in the action contract.
The plugin contains these skills:
| Skill | Status | What it does |
|---|---|---|
| embodied-control | v0 | The observe–act loop: small moves, reading stop reasons, verifying grasps, releasing in a separate call |
| robot-profile | v0 | Keep a profile of the robot: arms, cameras, frames, calibration and measured behavior |
| task-experience | v0 | Write a lesson after every episode, read relevant lessons before the next, promote repeated lessons to rules |
| object-segmentation | Coming soon | Open-vocabulary segmentation of camera images |
| depth-ranging | Coming soon | Pixel to 3D position from depth and calibration |
Skills are grouped into three families that will keep growing:
Solo se muestra el principio; lee el resto en el repo