droidsight MCP Server

What this does

droidsight exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

DROIDSIGHT_DEVICE_SERIAL
DROIDSIGHT_ADB_PATH
DROIDSIGHT_LOCAL_ROOT
DROIDSIGHT_DEVICE_PIN
DROIDSIGHT_ALLOW_SHELL
DROIDSIGHT_DEBUG_LOG
DROIDSIGHT_LOG
DROIDSIGHT_EVENTS
DROIDSIGHT_SENTINEL

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install droidsight?

Run the Claude Code command in the install section to add droidsight to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with droidsight?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to droidsight as well.

Does droidsight need an API key?

Yes. Before it can run, set these environment variables: DROIDSIGHT_DEVICE_SERIAL, DROIDSIGHT_ADB_PATH, DROIDSIGHT_LOCAL_ROOT, DROIDSIGHT_DEVICE_PIN, DROIDSIGHT_ALLOW_SHELL, DROIDSIGHT_DEBUG_LOG, DROIDSIGHT_LOG, DROIDSIGHT_EVENTS, DROIDSIGHT_SENTINEL. They go in the env block of your MCP config.