Skip to main content
Glama

lights-mcp

A made-up lights, read by voice. This is an MCP server that a voice assistant reaches through claude-voice, as one of its plugins.

It started from claude-voice's plugin template. The guide for writing one is docs/write-a-plugin.md in claude-voice, and docs/plugin-standard.md there holds the rules.

Try it

just setup
uv run lights-mcp status --simulate

The second line prints what the voice would hear, from the made-up lights in fake.py.

Related MCP server: Nordic Thingy:52 MCP Server

Install it in claude-voice

claude-voice plugins install lights --from <this folder>

It reads claude-voice-plugin.toml, writes config.default.toml as your first config, and ends with the usual typed-name approval.

What is where

Part

What it is for

src/lights_mcp/server.py

The MCP tools. Each answer carries a say, the sentence the voice reads aloud.

src/lights_mcp/service.py

The core: it asks the lights and words every answer, failures included.

src/lights_mcp/device.py

What the service needs from a lights. A real adapter answers it.

src/lights_mcp/fake.py

A made-up lights that refuses what the real one refuses.

src/lights_mcp/settings.py

The plugin's own config, from its own folder.

src/lights_mcp/platform/

The one place that knows the operating system.

scripts/ratchet.py

The quality levels, which may never get worse than main's.

scripts/mutate.py

Switches each rule off in turn, to prove its test can fail.

The checks

Every check is a recipe in the justfile, and CI runs the same lines. just check runs the ones a pull request needs, with no network.

just check
just commits
just ratchet

A new test must fail on the code before it, and the red-first job proves that. It runs only the test files a change touches. So it does not see a change to shared test setup, such as tests/conftest.py; say that in the pull request.

A rule is a line marked # RULE: what it says. Each one needs a test with its words as the name, and a row in scripts/mutations/.

A commit may carry Co-Authored-By and an outside contributor's Signed-off-by, and no other trailers. Any other note belongs in the pull request's text. just setup turns on the hook that says so early.

Cleaning up your own worktree

A session that worked in a worktree of its own removes it when it is done. Do it in this order.

  1. While scripts/.mutate-recovery.json exists, a mutation run of yours still has a line switched off. Stop that run with SIGTERM, and it puts the line back itself.

  2. Run the repair, which puts back a line a killed run left and runs nothing else.

  3. Check that git status shows nothing. A plain git worktree remove refuses a worktree with changes, and that refusal is the point: never add --force.

  4. Remove the worktree. Each run's temporary folder went with the run itself.

kill -TERM <the mutation run's process>
uv run python scripts/mutate.py --repair-only
git status --short
git worktree remove <the worktree's path>

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables control of lights in CASAMBI networks through Bluetooth interface without requiring APIs. Provides direct lighting control and management capabilities through natural language interactions.
      1
      GPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to directly interact with Matter devices and protocol operations, including device commissioning, attribute read/write, commands, and event monitoring, through natural language.
      7
      MIT