nvidia-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADB_PATH | No | Path to the Android Platform Tools adb executable. ADB must be on the MCP client's PATH, or this must be set to its full executable path. | adb |
| KODI_PORT | No | Kodi HTTP port. | 8080 |
| KODI_MOUNT | No | Absolute mounted .kodi path; if unset, ADB file access is used. | |
| SHIELD_HOST | Yes | Private LAN IP address of the NVIDIA Shield; one device per server instance. | |
| KODI_PASSWORD | No | Kodi HTTP password, separate from ADB authorization. | |
| KODI_USERNAME | No | Kodi HTTP username, separate from ADB authorization. | |
| SHIELD_ADB_PORT | No | Shield network debugging port. | 5555 |
| KODI_REMOTE_ROOT | No | Shared-storage root for ADB file access. | /sdcard/Android/data/org.xbmc.kodi/files/.kodi |
| KODI_MANAGER_PORT | No | Optional Kodi Manager port for the live Bingie / Kodi Manager adapter. | 8765 |
| KODI_MANAGER_TOKEN | No | Optional existing local Kodi Manager token for the live Bingie / Kodi Manager adapter. | |
| NVIDIA_MCP_STATE_DIR | No | Private snapshots and value-free audit records directory. Defaults to the OS user app-data directory. | |
| NVIDIA_MCP_ALLOW_WRITES | No | Explicitly allow mutation tools. Default operation is read-only. | 0 |
| NVIDIA_MCP_ALLOW_PLUGIN_BROWSE | No | Explicitly allow executing directory previews. Plugin browsing is separate because Files.GetDirectory executes installed add-on code and can make network requests. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shield_statusA | Inspect Shield model, Android version, memory, free storage and Kodi process. |
| shield_connectA | Connect ADB to the configured Shield only. Accept its debugging prompt on the TV. |
| shield_appsA | List installed Android package names (no app/account data). |
| shield_logcatA | Read a bounded Android log tail for native crashes. Redaction is best effort. |
| shield_screenshotA | Capture the current TV screen without navigation. Screens can contain private information. |
| shield_remoteB | Send one explicit remote button. Playback controls require permission and write mode. |
| kodi_lifecycleA | Start/stop/restart Kodi. Refuses playback; offline recovery/other-app interruption need explicit permission. |
| kodi_statusA | Inspect Kodi version, skin, current profile/window and active players; no playback changes. |
| kodi_addonsB | List installed add-on IDs, versions and enabled states; enabled is not proof of use/authentication. |
| kodi_readA | Run an allowlisted diagnostic JSON-RPC query. No arbitrary RPC, executebuiltin or playback calls. |
| kodi_logsB | Inspect redacted Kodi log tail and crash/stream/storage signals; safe while viewing. |
| kodi_read_fileB | Read a Kodi-relative text file (600 KB max) with redaction and original SHA-256. |
| kodi_backup_fileA | Save a private local rollback snapshot of one Kodi file. Does not modify the Shield. |
| kodi_backupsA | List the latest 50 private per-file snapshots without exposing their contents. |
| kodi_patch_fileA | Preview/apply exact before/after replacements. Writes need Kodi stopped, matching SHA and automatic backup. |
| kodi_restore_fileA | Restore one snapshot while Kodi is stopped; rejects stale checksums and creates an undo snapshot. |
| kodi_addon_settingsC | Search/page redacted settings in the active profile; Manager includes schema/defaults, otherwise saved XML only. |
| kodi_settingsB | Search/page Kodi's expert settings with current/default values, avoiding a whole-schema dump. |
| kodi_set_addon_settingB | Change a non-credential setting on a verified add-on version; backed up. Without Manager, stop Kodi first. |
| kodi_set_settingA | Change one non-credential Kodi setting through its runtime API, with a guisettings.xml rollback snapshot. |
| kodi_browseB | Preview one page of actual provider/library folders; opt-in, idle-only. No recursive loading or playback. |
| kodi_manager_inspectB | Optional Kodi Manager 0.3.9: inspect saved Bingie hubs/rows, sources, pipeline, health or fix status. |
| kodi_layout_previewC | Optional Manager: stage existing section rows with section_id and expected_revision; no layout write. |
| kodi_layout_applyB | Optional Manager: apply the exact staged plan within 10 minutes; Manager backs up and rejects stale revisions. |
| kodi_layout_rebuildA | Optional Manager: request one skin-menu rebuild while Kodi is idle. Inspect TV after it finishes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit_kodi | Run a focused, non-disruptive Shield/Kodi audit. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| repair_playbook | Practical lessons from Shield/Kodi repairs, accounts, source selection and Bingie configuration. |
| configuration | Configured capabilities without passwords, tokens or local paths. |
TDQS
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.