Back to directory

droid-mcp

An Android SDK that gives large language models typed, structured access to phone capabilities such as calendar, contacts, SMS and sensors through the Model Context Protocol, with everything staying on the device.

droid-mcp

droid-mcp implements the Model Context Protocol on Android, exposing 145 tools across 53 independent modules that cover calendar, contacts, SMS, camera, location, sensors, notification handling, accessibility-driven UI control, IME typing, a floating overlay, and shell or root administration through Shizuku or libsu. Any MCP client can call these tools over the local network once the phone's MCP server is started, or an on-device LLM app can call the underlying Kotlin functions directly without MCP at all.

The phone broadcasts itself on the local network through mDNS, and a sample app's pairing QR code encodes the connection URL and token so a desktop client such as Claude Code or Cursor can scan and connect without typing an IP address by hand. The library never requests permissions itself; the host app checks each module's required permissions and shows its own permission UI before registering that module's tools, so only the permissions for included modules are added to the app's manifest.

More in MCP servers

See all 734
  • Light Cloud

    light-cloud.com

    A hosting platform that deploys a static site, a container, or a managed Postgres database straight from a GitHub, GitLab, or Bitbucket push, with a preview URL for every branch and an MCP server for deploying from Claude Code.

  • ForensicDbg

    forensicdbg.com

    A post-mortem debugger for native Windows x86 and x64 crashes, with an MCP interface so AI tools can consume crash-dump analysis directly.

  • Karada.ai

    karada.ai

    A CI/CD platform that auto-compiles existing APIs into Go MCP servers, attaches composable middleware, and exposes them through one gateway usable from Cursor, Claude Code, and Windsurf.