Mcp Philips Hue

io.github.m2ai-mcp-serversPublished by GitHub account m2ai-mcp-serversv1.0.0Updated Oct 24, 2026

MCP server for Philips Hue smart lighting control

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

A local MCP server that lets an assistant control Philips Hue smart lighting through a Hue Bridge on the local network.

What you can do
Connect to a Philips Hue Bridge using its IP address and an API key, so an assistant can reach the lights on that bridge. Control Hue smart lighting from the assistant, for example switching lights on or off and adjusting them. The manifest lists no individual tools, so the exact set of lighting actions is not documented here.
When to use it
Worth adding when you have a Philips Hue Bridge and want an assistant to operate your smart lights, for example turning them on or off or adjusting them as part of a routine.
Requirements
Runs as a local process on the user's machine (npm package, stdio transport), desktop only. Needs the Hue Bridge IP address in HUE_BRIDGE_IP and a Hue Bridge API key in HUE_API_KEY, plus network access to the bridge.
Before you install
Requires a Hue Bridge API key (HUE_API_KEY) and the bridge's IP address; treat the key as a secret. The assistant can change the state of physical lights, so unintended switching or brightness changes are possible. No tool list is published, so review what actions it exposes before use.

Installation

In SourceWeft

  1. Open Mcp Philips Hue in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.