๐Ÿ

Python SDK

gestura-ring-sdk ยท planned

The Python SDK is in planning: PyO3/maturin native bindings over the same Rust protocol core the TypeScript SDK uses, asyncio-first, with mock, simulator, and BLE transports arriving in that order. The plan is published as sdk/python/PLAN.md in the gestura-app repository.

Installation

Nothing is published to PyPI yet โ€” install instructions will appear here with the first release. Until then, follow the plan and progress in the public repository.

Current integration shape

  1. Normalize gesture and haptic events into stable Python-side application semantics.
  2. Expose only the MCP tools and resources your external agent actually needs.
  3. Keep orchestration, approvals, and domain logic in your Python host while the MCP boundary stays deliberately small.

Features

  • โœ“
    Async host workflows

    Use asyncio to coordinate protocol traffic, gesture processing, and approvals without blocking.

  • โœ“
    Typed gesture semantics

    Model gesture payloads clearly before they become protocol-visible capabilities.

  • โœ“
    Protocol adapter friendliness

    A good fit for Python services that host MCP-facing integrations around a richer internal runtime.

  • โœ“
    Boundary-first architecture

    Keep the exposed surface small and use internal services for the heavier orchestration work.

  • โœ“
    Gesture MCP scope for now

    Positioned around gesture MCP integration at the moment, not a full top-to-bottom Python SDK story yet.

API Reference

MCP integration guidance

Use the MCP documentation to shape your Python host, define boundaries, and expose curated gesture capabilities safely.

View MCP integration docs โ†’

More Resources