v1.5.7

Magic Frame has had an MCP server since 1.5.0 — and nothing in the app said so. This release makes it visible, and gives agents the everyday things to do.

Agents can keep the household

Thirteen new tools cover what the companion API has always done: notes on the wall (post_message, optionally with a picture and an expiry), the shopping list (add, tick off, clear), to-dos (add, finish) and timers (start, stop) — each with a tool to list them. So "add milk and eggs to the shopping list" or "put dinner at seven on the kitchen screen for two hours" now works from Claude Code.

They have the same rights as the companion API: any token may use them, a viewer's too. Changing views and steering the displays stays with admin tokens. Ticking off and finishing set a state rather than flip it, so an agent that repeats itself does not undo its own work. control_displays also learns next_wallpaper.

Where to find it

Settings → Devices & apps has a new card, MCP server for AI agents, with your server's address and a ready-made command for Claude Code:

claude mcp add --scope user --transport http magic-frame http://<your-address>/api/mcp --header "Authorization: Bearer TOKEN"

Put your Companion API token from the card above in place of TOKEN. The new wiki page Agents and MCP has the rest: connecting, every tool by role, what keeps an agent from breaking things, and what an agent's AI service gets to see.

Not yet

The connectors in the Claude apps and the MCP integration in Home Assistant sign in with OAuth only, which Magic Frame does not offer yet — so those two cannot connect.

Upgrade: curl -fsSL https://raw.githubusercontent.com/jeremiaa/magic-frame/main/deploy/install.sh | bash — add-on users: add-on store → Reload → Update.