embodify-mcp 0.1.0a1__tar.gz

embodify_mcp-0.1.0a1/.claude-plugin/marketplace.json

@@ -0,0 +1,14 @@
+{
+  "name": "embodify",
+  "owner": {
+    "name": "Yida Yang"
+  },
+  "description": "Embodify: give your agent a body.",
+  "plugins": [
+    {
+      "name": "embodify-skills",
+      "source": "./embodify-skills",
+      "description": "Embodify skills: operate robots through the Embodify MCP server, keep a profile of the robot body and improve from experience."
+    }
+  ]
+}

embodify_mcp-0.1.0a1/.gitattributes

@@ -0,0 +1,7 @@
+* text=auto
+*.py text eol=lf
+*.md text eol=lf
+*.toml text eol=lf
+*.json text eol=lf
+*.yml text eol=lf
+*.html text eol=lf

embodify_mcp-0.1.0a1/.github/ISSUE_TEMPLATE/backend_request.yml

@@ -0,0 +1,41 @@
+name: Backend request
+description: Ask for support for a simulator, benchmark or robot.
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Tell us about the simulator, benchmark or robot you would like Embodify to support.
+        New backends are welcome as contributions too; see docs/backend-development.md.
+  - type: input
+    id: name
+    attributes:
+      label: Simulator, benchmark or robot
+      placeholder: e.g. RoboTwin, LeRobot SO-101
+    validations:
+      required: true
+  - type: input
+    id: link
+    attributes:
+      label: Link
+      description: Project page, repository or paper.
+  - type: textarea
+    id: embodiment
+    attributes:
+      label: Robot and sensors
+      description: Arms and grippers, mobile base, cameras and other sensors.
+  - type: textarea
+    id: interface
+    attributes:
+      label: Control interface
+      description: How it is controlled (Python API, ROS, vendor SDK), and its action and observation spaces if you know them.
+  - type: textarea
+    id: use
+    attributes:
+      label: What you would use it for
+  - type: checkboxes
+    id: contribute
+    attributes:
+      label: Contributing
+      options:
+        - label: I would like to help implement or test this backend.

embodify_mcp-0.1.0a1/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,55 @@
+name: Bug report
+description: Something does not work as described.
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the report. Leave out secrets, private host names and camera images you cannot share.
+        Report security vulnerabilities privately through the Security tab instead.
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened
+      description: What you did, what you expected and what happened instead.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: How to reproduce
+      description: Server command and options, and the tool calls involved if you have them.
+  - type: input
+    id: version
+    attributes:
+      label: Embodify version
+      description: The output of `embodify-mcp --version`.
+    validations:
+      required: true
+  - type: dropdown
+    id: backend
+    attributes:
+      label: Backend
+      options:
+        - fake or fake-two-arm
+        - libero
+        - robodojo
+        - remote
+        - other
+    validations:
+      required: true
+  - type: input
+    id: agent
+    attributes:
+      label: Agent host and model
+      placeholder: e.g. Claude Code with Claude Opus 5.5
+  - type: input
+    id: system
+    attributes:
+      label: Operating system and Python version
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: Server stderr, error messages or the relevant lines of events.jsonl.
+      render: text

embodify_mcp-0.1.0a1/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,16 @@
+name: Feature or skill request
+description: Suggest a tool, a skill or another improvement.
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: idea
+    attributes:
+      label: What you would like
+      description: The tool, skill or change, and the problem it solves.
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Context
+      description: The backend, agent and task where you need it, and any related work or papers.

embodify_mcp-0.1.0a1/.github/pull_request_template.md

@@ -0,0 +1,11 @@
+## What this changes
+
+<!-- What changed and why. Link related issues. -->
+
+## Checks
+
+- [ ] `python -m pytest -q` passes
+- [ ] `python tools/check_release.py` passes
+- [ ] Backend changes are tested on that backend, not only on Fake
+- [ ] Docs, both READMEs and the changelog are updated where needed
+- [ ] No credentials, personal host configuration, run logs or simulator assets

embodify_mcp-0.1.0a1/.github/workflows/ci.yml

@@ -0,0 +1,40 @@
+name: core
+on: [push, pull_request]
+permissions:
+  contents: read
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+        python: ['3.10', '3.12']
+        include:
+          - os: ubuntu-22.04
+            python: '3.8'
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+      - run: python -m pip install -e ".[dev,media,diagnostics]"
+      - run: python -m pytest -q
+      - run: python tools/check_release.py
+      - run: python -m build
+      - run: python -m twine check dist/*
+  installed-wheel:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - run: python -m pip install build
+      - run: python -m build
+      - run: python -m venv "$RUNNER_TEMP/embodify-verify"
+      - run: '"$RUNNER_TEMP/embodify-verify/bin/python" -m pip install dist/*.whl'
+      - working-directory: ${{ runner.temp }}
+        run: |
+          "$RUNNER_TEMP/embodify-verify/bin/embodify-mcp-smoke"
+          "$RUNNER_TEMP/embodify-verify/bin/embodify-mcp-smoke" --remote

embodify_mcp-0.1.0a1/.github/workflows/release.yml

@@ -0,0 +1,39 @@
+name: release
+on:
+  release:
+    types: [published]
+permissions:
+  contents: read
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - name: Tag matches package version
+        run: |
+          version=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml', 'rb'))['project']['version'])")
+          test "${GITHUB_REF_NAME}" = "v${version}" || { echo "tag ${GITHUB_REF_NAME} does not match version ${version}"; exit 1; }
+      - run: python -m pip install build twine
+      - run: python -m build
+      - run: python -m twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+  pypi:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/embodify-mcp/
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

embodify_mcp-0.1.0a1/.gitignore

@@ -0,0 +1,24 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.venv*/
+*.egg-info/
+build/
+dist/
+out/
+.env
+.env.*
+!.env.example
+*.local.json
+*.local.toml
+.codex/
+.claude/
+.mcp.json
+*.pem
+*.key
+*.safetensors
+*.ckpt
+*.pt
+*.pth
+*.hdf5
+*.h5

embodify_mcp-0.1.0a1/CHANGELOG.md

@@ -0,0 +1,36 @@
+# Changelog
+
+## 0.1.0a1 — First release
+
+Embodify gives your agent a body: an MCP server and a set of skills that let
+Codex, Claude Code and other agents control robots.
+
+**MCP server (`embodify-mcp`)**
+
+- Tools: `get_session_info`, `list_tasks`, `reset_task`, `observe`,
+  `move_relative`, `set_gripper`, `stop_episode`, and `control_arms` for
+  coordinated two-arm motion.
+- Backends: one- and two-arm Fake, LIBERO with all 130 tasks, and RoboDojo with
+  dual ARX X5 arms on all 54 simulation tasks, chosen by the agent or fixed by
+  the operator, each with its native episode limit unless overridden.
+- Remote backends over SSH or TCP, with heartbeats for slow links and
+  reconnection through `reset_task`.
+- Live monitor and replay: watch running episodes in a browser, or replay past
+  runs frame by frame, in English or Chinese.
+- MCP over stdio, protocol versions 2024-11-05 to 2025-11-25.
+- Commands: `embodify-mcp`, `embodify-mcp-backend`, `embodify-mcp-monitor`,
+  `embodify-mcp-preflight` and `embodify-mcp-smoke`.
+
+**Skills pack (`embodify-skills`)**
+
+- `embodied-control`, `robot-profile` and `task-experience`.
+- Coming soon: `object-segmentation` and `depth-ranging`.
+
+**Installation**
+
+- Plugin marketplace in `.claude-plugin/` for Claude Code and Codex: install the
+  skills with `claude plugin install embodify-skills@embodify` or
+  `codex plugin add embodify-skills@embodify`, and register the MCP server as
+  `embodify`.
+- One-line setup: agents install Embodify for themselves by following
+  `docs/agent-setup.md`.

embodify_mcp-0.1.0a1/CITATION.cff

@@ -0,0 +1,23 @@
+cff-version: 1.2.0
+message: "If Embodify helps your research, please cite it as below."
+title: "Embodify: Give Your Agent a Body"
+type: software
+authors:
+  - family-names: Yang
+    given-names: Yida
+version: 0.1.0a1
+date-released: 2026-10-02
+license: Apache-2.0
+repository-code: "https://github.com/YidaYang/embodify"
+url: "https://github.com/YidaYang/embodify"
+abstract: >-
+  Embodify lets the agent you already use, such as Claude Code or Codex, observe and
+  control robots through an MCP server and a pack of agent skills, with simulator
+  backends for LIBERO and RoboDojo.
+keywords:
+  - embodied AI
+  - robotics
+  - robot manipulation
+  - MCP
+  - LLM agents
+  - agent evaluation

embodify_mcp-0.1.0a1/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported privately to the project maintainer, Yida Yang, using the contact
+details on the maintainer's GitHub profile.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

embodify_mcp-0.1.0a1/CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contributing to Embodify
+
+Contributions are welcome: new simulators and robots, new skills, fixes and
+documentation. By taking part you agree to follow the
+[code of conduct](CODE_OF_CONDUCT.md).
+
+## Set up
+
+```sh
+python -m pip install -e ".[dev]"
+python -m pytest -q
+python tools/check_release.py
+```
+
+Core tests run without a GPU, simulator downloads, credentials or network
+access. To check an installed package, run `embodify-mcp-smoke` from outside
+the checkout.
+
+## Adding a backend
+
+To request support for a simulator or robot, open an issue with the backend
+request form. To add one yourself, follow [writing a backend](docs/backend-development.md).
+Add the backend to the contract test suite, document its setup in
+[backend setup](docs/backends.md) and add it to the backend table in both
+READMEs. Test changes to a simulator or robot backend on that backend, not only
+on Fake.
+
+## Adding a skill
+
+Create `embodify-skills/skills/<skill-name>/SKILL.md` with `name` and
+`description` in its frontmatter, and keep supporting files such as templates
+in the same folder. Write for the agent: concrete steps, what to check after
+each action and what to avoid. If you use Claude Code, check the skills pack
+with `claude plugin validate --strict embodify-skills/.claude-plugin/plugin.json`.
+List the new skill in both READMEs.
+
+## Changing action semantics
+
+Changes to motion, grippers or stop reasons need contract tests. Validate the
+whole input before moving any arm, never replay a timed-out movement
+automatically, and document units, frames and stop reasons in the
+[action contract](docs/action-contract.md).
+
+## Pull requests
+
+- Keep simulator and GPU imports lazy, so importing the core never loads them.
+- Put backend-specific dependencies in that backend's setup instructions, not in
+  the core package dependencies.
+- Do not commit credentials, personal host configuration, run logs or simulator assets.
+- Preserve third-party notices.
+
+Contributions are licensed under Apache-2.0 unless a file states otherwise.