Practical guide
nvidia-MCP vs ADB and Kodi JSON-RPC: which should you use?
Use ADB for direct Android debugging, Kodi JSON-RPC for Kodi's API, and nvidia-MCP when a local AI assistant needs a scoped tool interface built on those connections.
nvidia-MCP uses ADB and Kodi HTTP rather than replacing them. This guide is written by the nvidia-MCP maintainer and compares interfaces, not measured speed or security rankings.
| Interface | Role | What you handle |
|---|---|---|
| ADB | Android's command-line debugging bridge: device connection, shell, file transfer and package operations. | Device authorization, command scope, state checks and recovery planning for your commands. |
| Kodi JSON-RPC | Kodi's programmable interface for supported application, library, settings and player operations. | Transport/authentication, request construction and handling each method's result. |
| nvidia-MCP | A local stdio MCP server exposing selected Kodi and device workflows to a compatible assistant. | Configure one target, approve access, review proposed changes and validate results. |
What the MCP layer adds
The assistant gets named tools, a tool reference and a Kodi repair playbook. The server separates read-only inspection from write and provider-browsing opt-ins. Supported configuration repairs include previews, exact-match checks, backups and undo paths. Disruptive operations check playback and foreground state.
There is no arbitrary shell or unrestricted JSON-RPC passthrough tool. The standard tool profile keeps discovery focused; the full profile exposes advanced workflows with their existing gates. These boundaries help an assistant operate a known task, while direct ADB remains appropriate for an experienced developer who needs a command outside the server's scope.
When direct JSON-RPC is enough
If your own script needs a known Kodi method, use Kodi's published API and validate the response. You do not need an AI client or an MCP server just to query an application property. nvidia-MCP becomes useful when you want an assistant to combine connection readiness, profile context, add-on information and bounded diagnostic evidence.
When the browser companion fits better
For clicking through supported add-on settings and configuration backups yourself, use Kodi Manager. It runs inside Kodi and can also extend nvidia-MCP with supported Manager APIs. It does not provide unrestricted Android-device debugging.
Connections and limits still matter
ADB and Kodi HTTP are separate services. Check each one and use the configured private credentials. Manager has a third, profile-local token. Keep these services on a trusted network rather than exposing them directly to the internet.
The server is a free MIT-licensed prerelease running on Python 3.11+. Live evidence is limited to one customized Shield. Other Android-family devices need their own preparation and hardware validation; Apple TV support is experimental and uses a separate non-ADB backend. Neither the MCP layer nor a backup guarantees that a firmware restriction, failed APK upgrade or unavailable provider can be repaired.
Start with local assistant setup or follow an evidence-first playback diagnosis.