Onsense MCP Server

Android phone camera, sensors & files for any MCP client — local, no cloud, no ADB. Exposed over MCP by the onsense mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

On a clean PC, uvx doesn't exist yet and the command below will fail with "'uvx' is not recognized". The easiest fix: install the onSense app first, tap "Start PC setup helper", and open the shown address on your PC. It gives you a one-line command that installs uv, pairs, and registers the MCP server in one go — and because the PC connects out to the phone, it also sidesteps the Windows firewall entirely.

Adding it to your client

The server ships on PyPI as onsense, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration

You will need 2 environment variables: YOUR_PAIRING_TOKEN, PHONE_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• uv (provides uvx; downloads a managed Python automatically — no separate Python install needed) - The onSense Android app installed on a phone on the same local Wi-Fi network as your PC - An MCP-compatible AI client such as Claude Code, Codex, or any stdio MCP client ---

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the onsense mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by hufirst; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.