
Apple TV MCP
io.github.trevor-nicholsPublished by GitHub account trevor-nicholsv0.2.0Updated Oct 24, 2026
Local MCP server for semantic Apple TV control with optional screenshots.
Overview
A local MCP server that lets an AI assistant control an Apple TV — open apps, navigate, play media, type, adjust volume and power — and optionally take screensh
- What you can do
- Read device, connection, playback and media state, and inspect available capabilities and installed apps (status, capabilities, list apps). Open apps by name or bundle identifier, and open URLs or deep links. Press remote buttons (directions, select, back, home, menu) to navigate tvOS. Control playback: play, pause, stop, next, previous, seek to a position, skip forward or backward. Type text into a focused tvOS field, set or adjust volume, and turn the Apple TV on or off. Optionally capture a screenshot returned as native MCP image content so a multimodal agent can see the screen.
- When to use it
- Useful when you want an assistant to drive an Apple TV hands-on: launching apps, searching inside them, controlling playback and volume, or navigating interfaces that expose no direct API. The screenshot option suits multimodal agents that need to verify what actually appeared on screen after an action.
- Requirements
- Runs locally over stdio; Python 3.14 required, installed via uv or pipx. The Apple TV must be paired first with atvremote wizard, then selected with the configure command; the computer and Apple TV must be on the same local network. Screenshots need the separate appletv-screenshot helper plus a separate developer pairing via pymobiledevice3 remote pair. No cloud account, OAuth or HTTP endpoint.
Installation
In SourceWeft
- Open Apple TV MCP in the dashboard and add it to a workspace.
- 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
Apple TV MCP: A local MCP server that lets AI agents control — and see — your Apple TV
[Apple TV MCP — AI control and visual navigation for Apple TV]
Open apps, navigate tvOS, control playback, type searches, adjust volume, manage power, and take screenshots so a multimodal agent can actually inspect what happened.
Apple TV MCP turns your Apple TV into a locally controlled, visually observable device for MCP-capable AI agents.
No hosted backend. No custom Apple TV app. No cloud account.
Why Apple TV MCP?
Most Apple TV automation is blind.
A script can press Right or Select, but it usually has no idea what appeared on the screen afterward.
Apple TV MCP combines semantic control with point-in-time visual observation.
The result is a feedback loop an AI agent can actually use:
Semantic tools are still preferred whenever possible. Screenshots make the difference when the task requires navigating an interface that does not expose a direct API.
Install in seconds
Apple TV MCP requires Python 3.14.
Recommended
Or:
Then pair your Apple TV:
Configure Apple TV MCP:
Check the setup:
And start the MCP server:
From source
What can it do?
Apple TV MCP exposes fourteen tools grouped around what an agent actually wants to accomplish.
See
- Take a screenshot of the current Apple TV screen
- Read device, connection, playback, and media state
- Inspect available Apple TV capabilities
Apps
- List installed applications
- Open an application by name
- Open an application by bundle identifier
- Open deep links and custom application URLs
Navigate
- Up
- Down
- Left
- Right
- Select
- Back
- Home
- Menu
- Other supported remote actions
Remote navigation is intentionally treated as non-idempotent. Apple TV MCP does not blindly replay navigation commands after an uncertain connection failure.
Playback
- Play
- Pause
- Toggle play/pause
- Stop
- Next
- Previous
- Seek to an absolute position
- Skip forward or backward
Text
Type directly into a focused tvOS text field.
This is useful for:
- Search
- Usernames
- App navigation
- Query entry
Volume
- Read volume when available
- Set an absolute volume level
- Adjust volume relatively
Power
- Turn the Apple TV on
- Turn the Apple TV off
Power operations use different retry semantics so a reconnect attempt cannot accidentally wake a device immediately after a successful power-off command.
Give your agent eyes
The optional screenshot backend is what makes Apple TV MCP more than a remote control.
The MCP tool:
returns the current Apple TV screen as native MCP image content.
That means a multimodal MCP client can call the tool and inspect the returned image directly.
For example:
The model does not need access to a local screen.png path and does not receive base64 inside a text response.
The PNG itself is returned through MCP.
Screenshots are point-in-time
Apple TV MCP does not continuously watch the screen.
A screenshot describes what was rendered at the moment it was captured.
If the agent performs another action afterward, the previous screenshot may already be stale.
The intended pattern is:
Enable screenshots
Screenshot support is optional.
Apple TV control continues to work normally without it.
Install the separate helper:
The screenshot system uses a separate Apple developer / RemoteXPC pairing from the pairing used by pyatv.
Pair for developer access:
Then configure the screenshot helper for one Apple TV:
Verify everything together:
A healthy installation will report both Apple TV control and screen capture.
The screenshot helper has its own configuration, dependencies, and lifecycle. pymobiledevice3 is not imported by the main appletv-mcp package.
For deeper screenshot setup and transport troubleshooting, see:
Quick start
The complete happy path is:
Connect your MCP client
Apple TV MCP uses local stdio MCP transport.
Any MCP client capable of launching a local stdio server can use it.
A typical configuration looks like:
If Apple TV MCP is running from a cloned repository instead:
The server does not expose an HTTP endpoint and does not require OAuth.
Tools
The screenshot tool is the only tool that returns image content rather than a structured result.
How it works
Apple TV MCP keeps control and visual observation intentionally separate.
Control
Apple TV control is provided through pyatv.
Apple TV MCP adds a semantic application layer on top for:
- deterministic app resolution
- capability checking
- connection lifecycle
- safe retry behavior
- non-idempotent command protection
- normalized MCP results
The stable Apple TV identifier is authoritative.
The last known IP address is only an optimization. If the Apple TV changes addresses, Apple TV MCP can rediscover it by identifier and update the preferred host.
Vision
Screenshots use the separate appletv-screenshot helper.
The helper uses pymobiledevice3 to reach Apple's developer services over RemoteXPC and request a screenshot through DVT.
Its default transport strategy is:
The normal Wi-Fi userspace path does not require root or a permanently running tunnel daemon.
The helper exists as a separate process so its protocol stack, dependencies, pairing records, and failure modes remain isolated from Apple TV control.
pymobiledevice3 is confined to the separately distributed appletv-screenshot helper. The main appletv-mcp package does not import or bundle it; the two processes communicate through a narrow command-line/file contract.
Designed for agents
The MCP interface intentionally exposes semantic operations rather than raw Apple protocols.
An agent should think:
not:
When a semantic operation exists, use it.
Visual navigation is the fallback for interfaces that require it.
Privacy and security
Apple TV MCP is designed to remain local.
- No hosted Apple TV MCP backend
- No cloud account
- MCP uses local stdio transport
- Apple TV pairing credentials stay on the user's machine
- RemoteXPC pairing records stay with the screenshot helper
- Credentials are never MCP parameters
- Credentials are never returned to the model
- Keyboard text is not emitted into normal logs
- Screenshots are captured only when explicitly requested
- Screenshot bytes are not logged
- Screenshots are stored only in a private temporary directory during capture
- Temporary screenshot files are deleted after the MCP result is created
- Screenshot capture does not run automatically after commands
- The helper is launched without a shell
- No DRM circumvention is attempted
Debug mode also keeps raw pyatv protocol logging disabled because low-level Companion traffic can contain sensitive keyboard and pairing payloads.
Protected video
Streaming applications may protect video using DRM.
In that case, screenshots can contain:
while menus or playback controls remain visible.
That is expected.
Apple TV MCP does not interpret a black protected video region as proof that:
- playback failed
- the Apple TV turned off
- screenshot capture failed
and it does not attempt to bypass DRM.
Limitations
Apple TV MCP intentionally has a narrow initial scope.
One Apple TV
Each server configuration controls one Apple TV.
Multi-device routing is not currently part of the public MCP interface.
Screenshots are not video
apple_tv_screenshot captures one frame at a time.
There is no:
- continuous stream
- background screen monitoring
- screen recording
- automatic screenshot loop
Focus is visual, not semantic
pyatv does not provide a universal signal for the currently highlighted tvOS element.
An agent can use screenshots to infer focus where appropriate.
media_app is not foreground_app
Apple TV status may identify the application associated with current media metadata.
That does not independently guarantee which application is visually in the foreground.
Apple developer services can change
Screenshot support relies on Apple developer protocols exposed through pymobiledevice3.
tvOS changes may require future compatibility updates.
Screenshot support is optional
Every non-screenshot Apple TV MCP tool works without the screenshot helper installed.
Configuration
Apple TV MCP stores application configuration in the platform-standard config directory.
Typical settings include:
Pairing credentials are not stored in this file.
If an MCP host launches processes with a minimal PATH, set screen_capture.command to the absolute path of the screenshot helper.
Existing configuration files from Apple TV MCP v0.1 remain compatible.
Doctor
Run:
to diagnose the complete installation.
It checks areas such as:
Screenshot support is optional.
If the helper is not installed, Doctor reports it as skipped rather than treating Apple TV control as broken.
Troubleshooting
Apple TV not found
Confirm:
- the Apple TV is powered on
- the computer and Apple TV are on the same local network
atvremote wizardcompleted successfully
Then rerun:
Apple TV IP changed
That is expected.
Apple TV MCP identifies the configured device by its stable identifier rather than trusting an old IP address.
App will not open
Use:
to see the applications currently exposed by the device.
Application-name matching is deterministic rather than fuzzy.
Text entry fails
A text field must already be focused on the Apple TV.
Screenshot helper not found
Install it:
or configure Apple TV MCP with its absolute path.
Screenshot target is not configured
Run:
Screenshot pairing fails
Developer screenshot pairing is separate from atvremote.
Run:
Screenshot is black
Protected content may intentionally hide its video frame.
Try opening a tvOS menu or application interface and capture again.
Development
Clone the repository:
Install:
Run the complete root quality gate:
The screenshot helper is a separate Python project:
The root package deliberately does not depend on or bundle pymobiledevice3.
Live tests
Normal tests use fakes and do not require Apple hardware.
Read-only Apple TV integration tests are explicitly opt-in:
Tests that can change Apple TV state require an additional opt-in:
Never enable the live-write suite against a device you do not intend to control.
Contributing
Contributions are welcome.
Before opening a pull request:
If your change affects the screenshot helper, run its independent quality gate as well.
Please preserve the project's core architecture:
Avoid exposing raw Apple protocol details through the MCP contract unless there is a clear semantic reason.
License
This repository contains two separately distributed components.
Apple TV MCP
appletv-mcp is licensed under the MIT License.
It does not import, bundle, or distribute pymobiledevice3.
Apple TV Screenshot
The optional appletv-screenshot helper under
sidecars/appletv-screenshot/ is licensed under GPL-3.0-or-later.
The helper directly uses pymobiledevice3, which is also licensed
under GPL-3.0-or-later.
The two components communicate through a one-shot subprocess interface.
See LICENSING.md for the repository-wide map.
Built for a simple idea
AI agents are much more useful when they can verify the effects of their actions.
Apple TV MCP gives them both sides of that loop:
So instead of blindly pressing buttons, an agent can interact with tvOS, inspect the result, and decide what to do next.
Source: README.md at commit 930a9bc
Tools
0Version history
1- v0.2.0LatestSep 16, 2026
Score
50% 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
- License10 pts