Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Give your agent a body: observe and control simulated robots (LIBERO, RoboDojo) over MCP.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"embodify": {
"command": "uvx",
"args": [
"embodify-mcp"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add embodify -- uvx embodify-mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"embodify": {
"command": "uvx",
"args": [
"embodify-mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"embodify": {
"type": "stdio",
"command": "uvx",
"args": [
"embodify-mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 YidaYang 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.0a2)은 35일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, zanadir
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
Find what a repository's CI is missing, and which security checks cannot fail the build.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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:
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요