bl-halo-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bl-halo-mcp show 'Hello' on my Halo display"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
bl-halo-mcp

Fleet MCP wrapper for Brilliant Labs Halo smart glasses (2025 successor to Frame 2024). Open-source AI glasses: ~40 g wayfarer, 0.2 in 640x480 RGB microOLED peripheral HUD, low-power camera, dual mics + bone-conduction audio, IMU + taps/clicks, NPU SoC, Lua 5.4 frame.* VM over BLE, Noa companion AI with Narrative memory + natural-language Miniapps.
How it runs
Headless default: FastMCP stdio (uv run python -m bl_halo_mcp.server) + Starlette REST (11976) + Vite dashboard (11977). MOCK mode needs no hardware. Live needs BLE + paired Halo/Frame + Noa app.
Hands-in: display write, photo capture, Lua deploy, Noa ask. Hands-out: BLE pairing, firmware flash, store publish (drafts only here).
Related MCP server: btdiag
Hardware (open, documented)
Halo is fully documented open hardware: Balletto B1 (Cortex-M55 + Ethos-U55 NPU),
VGA global-shutter camera, dual mics, bone-conduction audio, tap-interrupt IMU,
300 mAh - see docs/HARDWARE.md and the dashboard Hardware
page with a 3D viewer for Brilliant's official full-assembly STL
(docs.brilliant.xyz/halo/halo.stl). No official CAD sources or firmware repo
exist yet (both "coming soon" upstream) - anything claiming otherwise is wrong.
Status: alive, small-batch (not dead, not Meta)
First Halo units shipped Aug 2026 after a bumpy ramp (production dates slipped repeatedly through H1 2026 - hinge/plastics tweaks, holiday shutdowns). Limited quantities, direct sale via brilliant.xyz ($299 pre-launch, now $349-399). Frame is discontinued/sold out. Company active: 2026 partnerships (Alif, Neuphonic, TheStage AI, Liquid AI), maintained docs/SDK/firmware.
Supply chain is China-centered (Brilliant has not named the assembly factory; schedules move with Chinese holidays; Far-East suppliers include Guozhao display, QST compass, Grepow cells). Design in Singapore/HK, fabless global BOM, assembly in China - the standard small-batch open-hardware play. Consequence for this repo: MOCK-first + emulator is the primary dev path for most people; live hardware is a bonus, not the baseline.
Quick start
Copy-Item .env.example .env
uv sync --extra dev
uv run pytest -q
.\start.ps1First time? Complete docs/ONBOARDING.md before expecting live host calls.
Documentation
Doc | Purpose |
Onboarding (mandatory: Halo/Frame, BLE, emulator, Noa costs) | |
Env + ports | |
Dev loop | |
Tool reference | |
Fixes |
Backend health: http://127.0.0.1:11976/api/health. Ports 11976/11977 registered in fleet WEBAPP_PORTS.md.
MCP tools (implemented)
halo_device- 21-op portmanteau (status, connect, show_text/image, photo, IMU, audio, Lua CRUD, Noa, Miniapp, firmware)halo_dashboard- Prefab App status cardhalo_help,halo_shutdown- help + guarded disconnectResource
skill://halo-dev/SKILL.md, prompthalo_recipe
Upstream: docs https://docs.brilliant.xyz, SDK https://github.com/brilliantlabsAR/brilliant_sdk, Noa https://github.com/brilliantlabsAR/noa-flutter.
Available Tools
4 toolshalo_dashboardA
Halo status dashboard (Prefab App).
Return Format
{success, message, app} where app renders device, battery, display, counts.
Examples
await halo_dashboard()
Inputs: no named parameters. Returns: object
halo_deviceC
Halo / Frame glasses controller (portmanteau).
Return Format
{success, message, result?, error?, suggestions?, has_more?}.
Examples
await halo_device("status")
await halo_device("show_text", text="Hello Halo")
await halo_device("capture_photo")
Inputs: operation (required), text, limit, offset, +3 more. Returns: object
halo_helpB
Halo help - operations, BLE pairing, Lua, Noa.
Return Format
{success, message, result: {topic, text}}.
Examples
await halo_help()
await halo_help("lua")
Inputs: topic. Returns: object
halo_shutdownA
Disconnect Halo (destructive-guarded).
Return Format
{success, message, result?}.
Examples
await halo_shutdown(confirm=True)
Inputs: confirm. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
halo_device is a catch-all that overlaps with halo_dashboard (status vs. full dashboard) and can perform many actions, making its boundary fuzzy. halo_help and halo_shutdown are distinct, but the general-purpose nature of halo_device creates ambiguity.
All tools share the consistent halo_ prefix and use snake_case, creating a recognizable family. However, the second part mixes nouns (device, dashboard) with verbs (shutdown) and a noun/verb (help), which is a minor inconsistency.
Four tools is a well-scoped set for a niche device controller, avoiding both bloat and thinness. Each tool has a clear role, even if halo_device is broad.
Core operations like status, display text, photo capture, help, shutdown, and dashboard are covered. Missing explicit connect/pair or settings tools, but help references BLE pairing and the surface feels adequate for typical use.
Maintenance
Related MCP Connectors
Automate 1,000+ services from any MCP-compatible AI agent: build Applets, run actions and queries.
Official MCP bridge to Exogram—the Personal AI Agent for your work, people, and life.
Use AI models for chat, image, and video generation from Claude Code and other MCP hosts.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables control of MentraOS smart glasses through tools for managing text displays, audio output, and input transcriptions. It integrates with Mentra Cloud to facilitate seamless interaction with smart glass hardware using natural language commands.4ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Bluetooth audio devices via MCP tools, including battery status, connect/disconnect, find-my, and snoop decoding.MIT
- AlicenseNot gradedqualityBmaintenanceControl macOS system settings, apps, windows, audio, displays, screenshots, and Focus mode via MCP.172 npm4Apache 2.0
- FlicenseNot gradedqualityBmaintenanceProvides MCP tools for screen capture, HID mouse/keyboard control, system and ESP status, and local Ollama chat/vision through a local MCP endpoint.-