Skip to main content

pylips-mcp

tests License: MIT Python 3.10+

MCP server for controlling Philips Android TV via the JointSpace API and ADB.

Exposes 14 tools covering power, volume, ambilight, app launching, and YouTube playback. Handles the TP Vision SHA1 certificate chain transparently.

Demo

MCP client: the 16 tools, then get_state on the real TV

Recorded against the real TV with docs/demo/record.sh: a minimal MCP client (docs/demo/mcp_demo.py) starts the server over stdio with TV_HOST/TV_USER/TV_PASS in the environment, lists the tools and calls get_state (read-only). Credentials never appear on screen.

Tools

Outil Rôle
power_on Allume la TV Philips
power_off Eteint la TV Philips (standby)
screen_off Eteint l'ecran de la TV tout en gardant le son actif (mode musique). Note: fonctionne principalement en source HDMI/TV, limite en mode Android.
screen_on Rallume l'ecran de la TV apres un screen_off
volume_up Augmente le volume de la TV (default +5)
volume_down Baisse le volume de la TV (default -5)
volume_set Regle le volume a un niveau specifique
mute Coupe ou remet le son de la TV
ambilight_on Active l'Ambilight de la TV
ambilight_off Desactive l'Ambilight de la TV
ambilight_mode Change le mode Ambilight
list_apps Liste les applications disponibles sur la TV
launch_app Lance une application sur la TV
youtube_video Lance YouTube sur une video specifique (URL youtube ou ID de video)
get_state Retourne l'etat actuel de la TV (allumee/standby)
send_key Envoie une touche de telecommande

YouTube ID extraction

extract_video_id is deliberately duplicated in catt-mcp (cast_youtube, Chromecast with start position and dual-screen sync). Both servers stay installable on their own; each one tests its copy with the same table of cases (tests/test_youtube_id.py). Decision recorded on 2026-09-20.

Requirements

  • Python 3.10+
  • pylips installed and accessible
  • Philips Android TV with JointSpace API enabled (2016+ models)
  • ADB enabled on the TV (for YouTube deep linking)
  • wakeonlan Python package (optional, for Wake-on-LAN)

Installation en une ligne

uvx pylips-mcp                 # depuis PyPI ; avant publication : uvx --from git+https://github.com/amineutron/pylips-mcp pylips-mcp

Configuration Claude Desktop / Claude Code (mcpServers) :

{ "pylips": { "command": "uvx", "args": ["pylips-mcp"], "env": { "TV_HOST": "192.0.2.10", "TV_USER": "...", "TV_PASS": "..." } } }

Setup

1. Pair with your TV

pip install pylips
python -m pylips --host 192.168.0.XX --init

This generates credentials saved in ~/.config/pylips/pylips.conf.

2. Install dependencies

pip install mcp requests wakeonlan

3. Configure

Copy config.example.yaml to config.yaml and fill in your TV credentials:

tv:
  host: "192.168.0.XX"
  user: "your_user"
  pass: "your_password"

pylips_path: "/path/to/pylips"  # or set PYLIPS_PATH env var

4. Run

python server.py

Or set via environment variables:

TV_HOST=192.168.0.XX TV_USER=xxx TV_PASS=xxx python server.py

Claude Desktop Configuration

{
  "mcpServers": {
    "philips-tv": {
      "command": "python3",
      "args": ["/path/to/pylips-mcp/server.py"],
      "env": {
        "TV_HOST": "192.168.0.XX",
        "TV_USER": "your_user",
        "TV_PASS": "your_password",
        "PYLIPS_PATH": "/path/to/pylips"
      }
    }
  }
}

SSL Note

Philips TVs present a TP Vision certificate chain from 2015 signed with SHA1. Modern OpenSSL and the Fedora/RHEL crypto policy reject SHA1 signatures, so a classic CA verification is impossible, even with the bundled chain and SECLEVEL=0.

What this server does instead, honestly:

  • CA verification is disabled (it cannot succeed);
  • the SHA-256 fingerprint of the certificate presented by the TV must match the leaf certificate shipped in tpvision_ca.pem (checked by urllib3 after the TLS handshake, so a man-in-the-middle cannot impersonate the TV without the private key). Verified against a real 55OLED705 (JointSpace 6, port 1926);
  • PYLIPS_TLS_FINGERPRINT=<sha256 hex> pins another TV, PYLIPS_TLS_PIN=0 disables pinning and logs a warning.

tpvision_ca.pem is the public TP Vision chain (leaf restfultv.tpvision.com, intermediate ca.tpvision.com, root www.tpvision.com, valid until 2042), extracted from a TV with openssl s_client -showcerts. It contains no secret.

License

MIT

Volume en HDMI ARC

Quand la TV est reliee a un ampli en HDMI ARC, le son ne sort pas de la TV : agir sur son volume n'a aucun effet audible. Si denon.host est renseigne dans la configuration, volume_up, volume_down, volume_set et mute sont donc rediriges vers l'ampli Denon ; sinon ils passent par l'API de la TV.

Pour piloter l'ampli directement (entrees, extinction, statut), utiliser denon-mcp.

Part of the Lyra ecosystem

Dépôt Rôle
lyra assistant DevOps vocal, local par défaut (AGPL-3.0)
fedora-agents MCP : machines virtuelles KVM et sauvegardes
mcp-tracking MCP + API + tableau de bord des tâches longues
neutroncore hub PWA du homelab
hue-mcp MCP Philips Hue (fork de ThomasRohde/hue-mcp)
pylips-mcp MCP TV Philips
denon-mcp MCP ampli Denon
catt-mcp MCP Chromecast et DLNA

Release files for pylips-mcp 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pylips-mcp 0.2.1
File Size Uploaded
pylips_mcp-0.2.1.tar.gz 21.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pylips-mcp 0.2.1
File Interpreter ABI Platform
pylips_mcp-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 41.5 kB

Release files / pylips_mcp-0.2.1.tar.gz

Download URL pylips_mcp-0.2.1.tar.gz
Size 21.9 kB
Tags Source
SHA-256 checksum
How to use checksums
619f28096cf3d4b8f3d9343d3868e007d9557a60351a44dec83d29fc93714de7
BLAKE2b-256 checksum
How to use checksums
bc28724f00a87582a4f1358057f9f741d2f97c7c39e73edb4743e25ebabb5983
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.

Transparency log

Release files / pylips_mcp-0.2.1-py3-none-any.whl

Download URL pylips_mcp-0.2.1-py3-none-any.whl
Size 19.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9e762e9439b6f2375b113f55a500ad60b31d12d2299aceef487594fa131b04ce
BLAKE2b-256 checksum
How to use checksums
3cf296e7b39bcb55c161c8163a67919b5b5527c9cef21dc83d63e05b51426057
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 release files

0.2.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page