This MCP server lets an AI assistant inspect, diagnose, and safely repair Kodi and Android TV/NVIDIA Shield setups, with read-only defaults and gated writes.
Inspect Shield model, Android version, memory, storage, and Kodi process; connect ADB; list apps; read bounded logs; capture screenshots; send remote buttons.
Inspect Kodi status, version, skin, profile/window, players, add-ons, allowlisted JSON-RPC diagnostics, redacted logs, and Kodi-relative files.
Back up Kodi files, preview/apply checksum-guarded replacements, restore snapshots, and change non-credential Kodi or add-on settings with rollback snapshots.
Browse provider/library folders one page at a time when explicitly enabled and idle.
Start, stop, or restart Kodi with playback and interruption safety checks.
Use optional Kodi Manager to inspect layout, sources, health, pipeline, and fixes; preview/apply staged Bingie layout plans; and request skin-menu rebuilds.
Writes, provider browsing, and Manager layout changes require explicit opt-ins; destructive actions use checksums, backups, and playback-state checks.
Uses Android Platform Tools/ADB against the Shield's Android TV system for shell-level inspection and control, including package listings, logcat, screenshots, foreground-app detection, and file access within the configured Kodi root.
Connects to Kodi's HTTP API and file system to diagnose issues (version, skin, profile, playback, add-ons, allowlisted JSON-RPC), tail and redact logs, back up and patch add-on/skin files, change settings with backup and readback, preview provider/library folders, and manage Bingie layouts.
Integrates with NVIDIA Shield TV over the LAN via ADB to inspect device status, list installed packages, read logcat, take screenshots, connect to the device, send explicit remote button presses, and start/stop/restart Kodi apps.
Click on "Deploy 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., "@nvidia-MCP Audit Kodi without interrupting playback and show redacted logs"
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.
Diagnose Kodi problems with your AI assistant. nvidia-MCP runs on your computer and lets an MCP assistant inspect Kodi, diagnose playback problems, preview repairs and apply changes with backups. It uses public ADB and Kodi HTTP interfaces on NVIDIA Shield, Android TV, Google TV and Android-based Fire TV. Apple TV support is experimental. No cloud account is required for the server.
Start here: Copy the guided setup prompt. You do not need the TV's IP yet; the agent explains where to find it.
0.5.12 prerelease. Read-only by default. Live evidence comes from one customized Shield; Fire OS, Google TV and Apple TV hardware validation is pending. See compatibility.
Inspect Kodi's version, profile, skin, add-ons, playback state and redacted logs.
Diagnose Android apps, connection readiness and native crashes; capture the TV screen.
Preview configuration repairs, then apply and undo them with checksum checks and private backups.
Inspect and upgrade local Android APKs with optional SDK tooling and recovery bundles.
Use optional Kodi Manager for live settings, playback routing, cached rows, configuration checkpoints and reviewed Bingie layouts.
The nvidia://playbook resource and audit_kodi prompt guide focused audits.
The default profile shows 10 everyday tools (9 on Apple TV, which has no ADB). Your agent can
enable the full profile for advanced file/APK repair; see the tool reference for profiles, permissions and limits.
Related MCP server: runtime-inspector-mcp
You need a computer, an assistant app that supports local MCP tools, and a TV on the same home network. Your assistant needs permission to run commands and edit files on the computer; it installs Python 3.11+ and other tools if needed. A browser chat alone cannot do this setup.
Give your agent one prompt.
Copy the complete setup request below.
No IP address or technical checklist is needed before you start.
Answer the agent's questions.
It asks which TV/device you use and gives the matching menu steps.
It explains how to find the IP, enable debugging where applicable, and enable Kodi remote control.
Reply after each step; the agent waits before continuing.
Approve the connection and let setup finish.
Select Allow on the TV when asked, or enter a pairing code through private input.
The agent verifies nvidia-MCP, then installs and connects Kodi Manager.
Once it confirms both work, ask: “Read the Kodi repair playbook and audit Kodi without interrupting anything.”
Use an assistant that can run commands, edit files and use local MCP tools on your computer. Have Kodi installed, keep your TV remote handy, and connect the TV and computer to the same home network.
Copy and paste.
Expand Show the setup prompt to copy below and copy the whole text box into your agent.
No editing is needed. You do not need to know the TV's IP address yet.
Follow the conversation.
The agent asks which TV you have, then explains the relevant settings and IP-address menus.
Reply after each step. It waits for missing details and permission prompts before continuing.
One prompt starts the setup; you will still answer questions and use the TV remote when needed.
Help me set up nvidia-MCP on this computer, then install and connect
Kodi Manager on my TV:
https://github.com/glasgowm148/nvidia-MCP
https://github.com/glasgowm148/kodi-manager
Read nvidia-MCP's docs/agent-setup.md and docs/companion.md first.
If not already known, first ask which TV/device I use. Do not assume I
know its IP address or have enabled debugging. Ask one short question
at a time. Explain the exact menus for my device, what to select and
what information to read back. Guide my device's TV preparation, including
debugging where applicable, finding its IP and enabling Kodi HTTP control.
For Apple TV, use the separate tvOS instructions. If a menu differs,
ask what I see. Wait for my reply before moving to the next TV step.
Do not invent connection details or scan my network.
Ask for the IP address on its own and wait for my answer. Only then ask
about a required port in a separate reply. Never request the IP and port
together, even as an optional extra. Ask about Kodi's HTTP port and any
Wireless debugging pairing port in separate replies too. Reuse details
I have already supplied.
Once TV preparation is ready:
1. Install and configure nvidia-MCP. Verify the actual MCP connection
can read my TV and Kodi before continuing.
2. Install Kodi Manager from https://glasgowm148.github.io/kodi-manager/
using Kodi's native installer. Reuse supported existing installations
and back up customizations before any replacement.
3. Connect the active profile's Manager token privately. You cannot change
Kodi Manager's own settings, so ask me to turn on Allow LAN access under
Kodi Manager → Configure → Dashboard. Then give me its browser address
and verify read-only Manager access.
Handle computer commands, downloads and supported TV navigation yourself.
Ask me for details or TV actions your tools cannot obtain or complete.
Request passwords, tokens and pairing codes only through private input.
Preserve my other MCP servers and settings. Target only my specified TV
and never interrupt playback. Enable only writes needed for setup;
finish with write mode and provider browsing off.
Continue both setup stages in this conversation, waiting for my replies
whenever information or permission is needed.Full instructions
TV menu steps, if you prefer to prepare the TV yourself.
Apple TV setup, experimental.
Vega OS Firesticks are unsupported; check the device guide.
flowchart LR
A[Your assistant] -->|MCP · stdio| B[nvidia-MCP on your computer]
B -->|ADB + Kodi HTTP| C[Android TV or Fire OS / Kodi]
B -.->|Optional settings and layout API| D[Kodi Manager inside Kodi]Each server instance targets one explicitly configured device. Apple TV uses an opt-in backend and separate configuration. Credentials and recovery files stay in your private local storage.
Kodi Manager runs inside Kodi and adds a browser dashboard, live add-on settings, playback pipeline inspection and supported Bingie layout editing.
Current optional companion UI, captured with synthetic demo data in view-only mode. The MCP server itself is a stdio service.
Download the shareable MP4 · Text walkthrough and captions
This shows the optional browser dashboard. Silent, edited capture with synthetic data in view-only mode; no TV was connected.
Already using nvidia-MCP?
Ask your agent: “Install Kodi Manager and connect it to nvidia-MCP.”
Follow agent-assisted setup.
Only want the browser dashboard?
Follow Kodi Manager's TV remote steps.
Install from its Kodi repository; no computer file transfer is needed.
Need an offline or pinned version?
Use the bundled ZIP instructions.
Repository installations receive preview updates through Kodi's update settings.
Writes and provider browsing have separate opt-ins. Inspect and preview before enabling changes. Disruptive tools check playback and the foreground app; unknown viewing state blocks them. Manager writes also require its own write mode. Layout editing requires reviewed Bingie / Skin Shortcuts versions and source hashes; unknown variants stay view-only.
Use a trusted LAN and keep credentials, logs and backups private. Repair tools have platform-specific limits; the optional Android profile-relaunch helper needs separate private deployment. See operation rules, repair workflows, APK recovery and Apple TV limits.
The complete generated tool catalogue lists Android/Shield tools and access gates. Apple TV has a separate capability table.
skills/nvidia-shield-kodi is a standard SKILL.md skill that
tells an agent when to use these tools and how to stay safe with them: triage order, common
playback/audio/add-on recipes, write and undo rules, and the setup flow when the server is missing.
Install the skill free from Agensi,
or copy the folder into your agent's skills directory (for example ~/.claude/skills/). It contains
only instructions and needs this MCP server installed.
Run the offline checks from a checkout before connecting a device. The suite uses synthetic credentials and fixtures; it does not contact a TV:
python3 -m pytest -q
ruff check --no-cache .
CHECK_DIST="$(mktemp -d)"
python3 -m build --outdir "$CHECK_DIST"
python3 scripts/check_release.py "$CHECK_DIST"/*.whl "$CHECK_DIST"/*.tar.gzKeep NVIDIA_MCP_ALLOW_WRITES=0 and NVIDIA_MCP_ALLOW_PLUGIN_BROWSE=0 for the first live
connection. The server targets one explicitly configured device and will not discover or scan
other devices. Read operation rules before enabling either capability.
Start with the documentation index, or go directly to:
I want to… | Guide |
Set up a TV and assistant | |
Connect Android / Fire TV or Apple TV | |
Use the dashboard and live settings | |
Configure access or repair a problem | |
Check support or reuse the Python code |
Contributing · Changelog · Security · MIT license. Independent project; not affiliated with NVIDIA, the Kodi Foundation or any add-on author.
List installed add-on IDs, versions and enabled states; enabled is not proof of use/authentication.
Inputs: enabled_only. Returns: object
Search/page redacted settings in the active profile; Manager includes schema/defaults, otherwise saved XML only.
Inputs: addon_id (required), limit, query, start. Returns: object
Save a private local rollback snapshot of one Kodi file. Does not modify the Shield.
Inputs: path (required). Returns: object
List the latest 50 private per-file snapshots without exposing their contents.
Inputs: no named parameters. Returns: object
Preview one page of actual provider/library folders; opt-in, idle-only. No recursive loading or playback.
Inputs: path (required), limit, start. Returns: object
Optional Manager: apply the exact staged plan within 10 minutes; Manager backs up and rejects stale revisions.
Inputs: preview_id (required). Returns: object
Optional Manager: stage existing section rows with section_id and expected_revision; no layout write.
Inputs: plan (required). Returns: object
Optional Manager: request one skin-menu rebuild while Kodi is idle. Inspect TV after it finishes.
Inputs: no named parameters. Returns: object
Start/stop/restart Kodi. Refuses playback; offline recovery/other-app interruption need explicit permission.
Inputs: action (required), interrupt_other_app, allow_offline_recovery. Returns: object
Inspect redacted Kodi log tail and crash/stream/storage signals; safe while viewing.
Inputs: lines, previous. Returns: object
Optional Kodi Manager 0.3.9: inspect saved Bingie hubs/rows, sources, pipeline, health or fix status.
Inputs: area (required). Returns: object
Preview/apply exact before/after replacements. Writes need Kodi stopped, matching SHA and automatic backup.
Inputs: path (required), edits (required), expected_sha256 (required), dry_run. Returns: object
Run an allowlisted diagnostic JSON-RPC query. No arbitrary RPC, executebuiltin or playback calls.
Inputs: method (required), params. Returns: result
Read a Kodi-relative text file (600 KB max) with redaction and original SHA-256.
Inputs: path (required). Returns: object
Restore one snapshot while Kodi is stopped; rejects stale checksums and creates an undo snapshot.
Inputs: backup_id (required), expected_current_sha256 (required). Returns: object
Change a non-credential setting on a verified add-on version; backed up. Without Manager, stop Kodi first.
Inputs: value (required), setting (required), addon_id (required), expected_version (required). Returns: object
Change one non-credential Kodi setting through its runtime API, with a guisettings.xml rollback snapshot.
Inputs: value (required), setting (required). Returns: object
Search/page Kodi's expert settings with current/default values, avoiding a whole-schema dump.
Inputs: limit, query, start. Returns: object
Inspect Kodi version, skin, current profile/window and active players; no playback changes.
Inputs: no named parameters. Returns: object
List installed Android package names (no app/account data).
Inputs: no named parameters. Returns: object
Connect ADB to the configured Shield only. Accept its debugging prompt on the TV.
Inputs: no named parameters. Returns: object
Read a bounded Android log tail for native crashes. Redaction is best effort.
Inputs: lines. Returns: object
Send one explicit remote button. Playback controls require permission and write mode.
Inputs: button (required), allow_during_playback. Returns: object
Capture the current TV screen without navigation. Screens can contain private information.
Inputs: no named parameters.
Inspect Shield model, Android version, memory, free storage and Kodi process.
Inputs: no named parameters. Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 25 tools
Most tools map cleanly to a distinct resource+action, and the settings family (kodi_settings vs kodi_addon_settings vs kodi_set_setting vs kodi_set_addon_setting) is carefully differentiated by object and read/write. A few pairs like kodi_backup_file/kodi_backups and kodi_patch_file/kodi_set_setting require close reading, but boundaries are largely clear.
All names use lowercase snake_case with consistent shield_/kodi_ namespace prefixes, and verbs are predictable (read, patch, restore, set, preview, apply). Some entries are noun-only (kodi_status, kodi_addons, kodi_logs) rather than verb_noun, a minor deviation but still readable and grouped.
25 tools is heavy for what is essentially a Shield/Kodi inspection-and-safe-edit server, and the surface sits right at the borderline where maintenance and selection cost grow. The extensive safety-related variants (backup/patch/restore, manager layout trio) are arguably each justified, but a leaner surface would reduce cognitive load.
The surface covers device lifecycle and diagnostics, logs, file read/backup/patch/restore round-trips, settings and add-on settings, and optional Manager layout staging/apply/rebuild, giving strong lifecycle coverage. Only minor gaps remain, such as no dedicated file-delete or broader addon-management operations, which agents can work around.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Scans remote MCP servers for protocol, security, and TLS issues; exposes scan tools via MCP.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.