Skip to content

Releases: nolte/reachy-mini-mcp

Release list

v0.1.1

v0.1.1 Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 May 18:43
v0.1.1
33d92e5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Changes

  • No changes

Project context

Audiences served

  • Reachy Mini owners / developers → addressed by §Runtime requirements, §Migration notes for operators
  • Reachy Mini hardware (safety boundary) → addressed by §Hardware support

Runtime requirements

  • Python >=3.12 is now the floor for the runtime (pyproject.toml, commit a347af9).
  • Pinned runtime dependencies: mcp>=1.2.0, httpx>=0.27.0 (commit d4a3858, requirements.txt).
  • Distribution remains the Docker image built from the repo Dockerfile; the audit log is written under ${XDG_CACHE_HOME}/reachy-mini-mcp/ (commit a347af9, src/reachy_mini_mcp/server.py).
  • The daemon URL is configured via REACHY_MINI_DAEMON_URL, defaulting to http://127.0.0.1:8000 (commits a347af9, b50b44a).
  • A reachable Pollen reachy-mini daemon on the configured URL is an external precondition.

Migration notes for operators

  • This is the initial release line; no prior version to migrate from.
  • The shipped .mcp.json carries the localhost default for REACHY_MINI_DAEMON_URL (commit a347af9); operators using a non-localhost daemon (e.g. Wireless mDNS http://reachy-mini.local:8000) must override the env var explicitly.
  • The audit-log directory under ${XDG_CACHE_HOME}/reachy-mini-mcp/ must be writable by the container's mcp user; the default Docker run command bind-mounts ${HOME}/.cache/reachy-mini-mcp (.mcp.json).

Hardware support

  • Tier-1 read-only tools implemented in this release: health_check, get_motor_status (commits a347af9, c954b7b, src/reachy_mini_mcp/server.py). Tier-2 (motion-safe) and Tier-3 (motion-active) tools are not yet implemented.
  • Platform coverage (Wireless / Lite / Simulation) has not been end-to-end validated against this server in CI; see open question below.
  • The safety-boundary contract from the canonical spec (spec/reachy-mini/mcp-server/de.md) — pose-range validation against control-surface, safe-torque wrapping around motor toggles, audit trail per invocation — applies once tier-2/3 tools land; the tier-1 read surface inherits no write-side gates.

Open questions

  • The Python-application section bundle does not directly address four primary audiences from AUDIENCES.md: MCP clients, Repository maintainer, Pollen Robotics, Anthropic / MCP spec maintainers. Future bundle iterations should add audience-targeted sections (e.g. tool-inventory diff for MCP clients, daemon-endpoint coverage for Pollen, MCP capability-handshake notes for Anthropic).
  • Spec-drift mechanism between this implementation and spec/reachy-mini/mcp-server/{de,en}.md remains informal (AUDIENCES.md §Open questions).
  • Tier-2 / Tier-3 tool implementation is pending and gates the hardware-support story above.
Assets 2
Loading