kef-mcp
Allows controlling Spotify playback on KEF speakers, including play, pause, skip, volume control, and searching for tracks or playlists to play.
Click on "Install 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., "@kef-mcpplay some jazz on the KEF speakers"
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.
kef-mcp
An MCP server for controlling KEF wireless speakers (LSX II / LS50 Wireless II / LS60) and playing Spotify on them. Exposes tools any MCP client can call to power the speaker on/off, switch inputs, set volume, control transport, and start Spotify playback — with one combined tool that does the whole "wake → switch to wifi → play" flow.
Built to be driven by Poke (see poke/), but it's a
standard MCP server (streamable HTTP) usable by any MCP client.
MCP client ──► kef-mcp ──┬─ HTTP ─► KEF speaker (LAN)
└─ HTTPS ► Spotify Web APITools
Tool | What it does |
| Main one. Wake KEF → source=wifi → find on Spotify → play on KEF. |
| Power on / off. |
| wifi, bluetooth, tv, optic, coaxial, analog. |
| Hardware volume 0-100. |
| Transport control. |
| Power, source, volume, now playing. |
| Spotify-side control. |
| Volume on the active Spotify device. |
| Track / artist / device. |
Prerequisites
Spotify Premium (the Web API blocks playback control on Free accounts).
A KEF LSX II / LS50 Wireless II / LS60 on your LAN, ideally with a DHCP reservation so its IP is stable.
Docker (to run the server), or just Python 3.12+ to run it directly.
Setup
1. Configure
cp .env.example .envFill in .env:
KEF_HOST— the speaker's LAN IP (from the KEF Connect app or your router).KEF_DEVICE_NAME— substring of its Spotify Connect name (e.g.KEF).SPOTIFY_CLIENT_ID/SPOTIFY_CLIENT_SECRET— from a Spotify app (Redirect URI:http://127.0.0.1:8888/callback).MCP_AUTH_TOKEN— a random string clients must send as a Bearer token. Generate:python -c "import secrets; print(secrets.token_urlsafe(32))"
2. Get a Spotify refresh token (once)
pip install requests
export SPOTIFY_CLIENT_ID=... # PowerShell: $env:SPOTIFY_CLIENT_ID="..."
export SPOTIFY_CLIENT_SECRET=...
python auth_spotify.pyLog in, approve, and copy the printed SPOTIFY_REFRESH_TOKEN=... line into .env.
3. Run
Docker (recommended):
docker compose up -d --build
docker compose logs -f kef-mcp
docker-compose.ymlalso runs apoke-tunnelsidecar that forwards the MCP server up to your Poke agent (seepoke/README.md). SetPOKE_API_KEYin.envto enable it; it's only needed for Poke.
Or directly:
pip install -r requirements.txt
python server.py # serves streamable HTTP at http://0.0.0.0:8000/mcp4. Connect a client
Poke: set
POKE_API_KEYin.envand rundocker compose up -d— thepoke-tunnelcontainer connects it automatically. Full guide + the recipe:poke/README.md.Other MCP clients: point them at
http://<host>:8000/mcp. (If you expose the server beyond the tunnel, setMCP_AUTH_TOKENand sendAuthorization: Bearer <token>.)
Sanity checks
KEF reachable from the container:
docker compose exec kef-mcp python -c \
"import asyncio, os; from kef_client import KefClient; \
print(asyncio.run(KefClient(os.environ['KEF_HOST']).get_status()))"Should print the speaker status (e.g. standby / powerOn).
Notes & troubleshooting
"KEF Spotify Connect device not found" — the KEF only advertises as a Connect target once it's awake and has played Spotify since boot.
play_on_kefwakes it first; on a cold boot, cast to it once from the Spotify app, then retry.Spotify 404 / "No active device" — same cause; ensure
KEF_DEVICE_NAMEmatches the name Spotify shows.Container can't reach the KEF — verify
KEF_HOSTand that the speaker has a DHCP reservation.KEF API — writes are
POST /api/setData(JSON body), reads areGET /api/getData. Verified against LSX II / LS50 W II / LS60 firmware. Very old firmware used GET-only; update firmware if writes fail.
Project layout
kef-mcp/
├── server.py # MCP server: defines the tools
├── kef_client.py # KEF local HTTP API client
├── spotify_client.py # Spotify Web API client
├── auth_spotify.py # one-time Spotify OAuth helper
├── Dockerfile
├── docker-compose.yml # server + poke-tunnel sidecar
├── .env.example
├── tunnel/ # headless poke-tunnel container
│ ├── Dockerfile
│ └── entrypoint.sh
└── poke/ # Poke-specific: connection guide + recipe
├── README.md
└── RECIPE.mdSecurity
.envholds your Spotify secret/refresh token and auth token — gitignored, never commit it.Anyone with
MCP_AUTH_TOKEN+ the URL can control your speakers and Spotify. Keep it secret; consider a Cloudflare Access policy for remote exposure.
Credits
KEF local-API payload formats verified against pykefcontrol (MIT).
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nqrwhal/kef-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server