pyBittle-mcp-server

Name: pyBittle-mcp-server
Author: cluesang

@cluesang

代码仓库

关于 pyBittle-mcp-server

MCP Server to control pyBittle via BLE

基本信息

分类

其他

运行时

python

传输方式

stdio

发布者

cluesang

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "pyBittle-mcp-server": {
      "command": "uv",
      "args": [
        "pip",
        "install",
        "-r",
        "requirements.txt"
      ]
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is pyBittle-mcp-server?

pyBittle-mcp-server is a Python MCP (Model Context Protocol) server for controlling the Bittle robot via Bluetooth. It exposes movement and pose commands such as forward, backward, turn, sit, and rest, making them accessible through any MCP‑compatible client.

How to use pyBittle-mcp-server?

Install uv and uvx, then set up dependencies using the provided start_server.sh script or by manually running uv pip install -r requirements.txt. Power on the Bittle robot in Bluetooth pairing mode and start the server with ./start_server.sh. Once running, use MCP tools (e.g., the MCP CLI) to invoke commands like mcp call move_forward.

Key features of pyBittle-mcp-server

Connects to Bittle via Bluetooth.
Exposes movement and pose commands (forward, backward, turn, sit, rest, etc.).
Integrates with MCP tools for remote and programmatic control.
Logs all activity to bittle_mcp.log.

Use cases of pyBittle-mcp-server

Remote control of a Bittle robot from any MCP‑compatible client.
Automating robot movements in scripts or AI‑driven workflows.
Integrating robot commands into larger MCP‑based systems.

FAQ from pyBittle-mcp-server

What does pyBittle-mcp-server do?

It acts as a bridge between the MCP protocol and the Bittle robot, allowing movement and pose commands to be sent via Bluetooth.

What are the system requirements?

Python 3.10+, uv, uvx, the pyBittle library, the mcp-server library, and a Bittle robot with Bluetooth enabled.

How do I connect the server to Bittle?

Ensure the Bittle is powered on and in Bluetooth pairing mode before launching the server. The server attempts to connect automatically and logs the status.

What if the server fails to start?

Check Bluetooth pairing and confirm no other process is using the Bittle connection. Review bittle_mcp.log for detailed error messages. If port conflicts occur, start_server.sh automatically handles killing existing server processes.

What commands are available?

Commands include move_forward, sit, rest, and others. All are decorated with @mcp.tool() in server.py and automatically registered with the MCP server. Use mcp call to invoke them.