huangjunsen0406/py-xiaozhi

Open-source AI assistant ecosystem with MCP integrations, multimodal workflows, IoT support, and cross-platform voice interaction.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 20th, 2026
Created on February 15th, 2025
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 736
Total Stargazers: 3,479 (+0)
Total Subscribers: 34 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 34 days
Stale 30+ days: 3
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (100)
  • enhancement (34)
  • documentation (8)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

py-xiaozhi is a lightweight, cross-platform AI assistant framework that enables multimodal interaction with IoT devices and embedded systems.

The tool addresses the challenge of connecting large language models to physical hardware across diverse platforms. It provides a Python-based async architecture that handles real-time voice streaming, vision-language tasks, and device control. The framework integrates Model Context Protocol (MCP) for extensibility, allowing developers to add custom capabilities through MCP servers and clients. This approach lets a single codebase run on desktop operating systems and resource-constrained embedded platforms without significant modification.

The project suits developers building voice assistants, robotics applications, or IoT systems that need to run on heterogeneous hardware. It targets both high-end platforms like desktop computers and low-power devices such as Raspberry Pi, ESP32, and Jetson Nano. The multimodal capabilities and built-in voice interaction make it particularly valuable for embodied AI applications where the assistant must perceive and act on the physical environment. Teams evaluating adoption should note that the framework is designed for scenarios where edge deployment matters—where running inference locally or controlling hardware directly is a requirement rather than an option.

The project shows active development with regular updates and maintains comprehensive documentation. The codebase demonstrates ongoing refinement of core functionality across multiple platforms. The maintainer engages with the community through multiple repository mirrors and accepts sponsorship, indicating sustained commitment to the project's evolution.