onsense — Phone Camera, Sensors & Files for PC AI Agents

Give your PC AI agents real-world eyes. onsense is the PC-side MCP broker for the onSense Android app: run uvx onsense pair on your PC, and Claude Code, Codex, or any MCP client can see through your phone's camera, read its sensors, and exchange files/clipboard — all over local Wi-Fi. No cloud relay. No ADB.

Codex, running on the PC, reads the phone's sensors and looks through its camera to answer — live, over local Wi-Fi.

Architecture

Android phone (onSense app)           PC (this package)           AI client
  HTTP provider :8080        ←→    stdio MCP broker          Claude / Codex / …
  camera frames, photos,           onsense serve               natural-language or
  sensors, QR pairing              onsense clip :8770          /onsense tool calls

• The phone runs an HTTP provider on port 8080. It exposes camera frames, recent photos, and sensor readings, all gated by a pairing token.
• The PC package (onsense) is a stdio MCP broker. It translates MCP tool calls from your AI client into HTTP requests to the phone.
• Discovery uses mDNS (_onsense._tcp.local.). If the phone's IP changes, the broker rediscovers it automatically — no manual reconfiguration needed.
• An optional clip bridge daemon on port 8770 lets the phone push camera frames, files, and clipboard content to the PC (and, if enabled, lets the phone pull from the PC clipboard).

Requirements

• Python 3.10+ and uv (provides uvx)
• 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

Quick Start

1. Pair your phone

Run this once. The PC prints a QR code; scan it from the onSense app ("Scan PC QR"). The phone pushes its address and token to the PC, which registers the MCP server automatically.

uvx onsense pair

After pairing, restart your AI client once so it picks up the new onsense MCP server.

2. Use it

Ask your AI client naturally:

"Take a photo of what's in front of my phone." "What are the current sensor readings?" "Show me the last 5 photos on my phone."

The MCP tools are called automatically. In Claude Code you can also use the bundled /onsense slash command (installed during pairing).

3. Diagnose problems

uvx onsense doctor           # checks Python, uv, MCP, Claude registration, mDNS, phone reachability
uvx onsense doctor --base http://192.168.1.5:8080 --token YOUR_PAIRING_TOKEN

Subcommands

Other MCP clients (Claude Desktop, Codex, …)

uvx onsense pair auto-registers the server with Claude Code (via claude mcp add) — this one-line auto-setup is Claude Code-specific. The MCP server itself is standard stdio MCP, so any MCP-compatible client works once you add it manually. Run uvx onsense pair once first: it saves your phone's address and token to ~/.onsense/pair.json, which the server reads at request time — so you don't put the token in each client's config, and the phone's IP is auto-tracked via mDNS.

Claude Desktop — add to claude_desktop_config.json:

{ "mcpServers": { "onsense": { "command": "uvx", "args": ["onsense", "serve"] } } }

Codex — register via the CLI (verified with Codex CLI 0.39.0):

codex mcp add onsense -- uvx onsense serve

or add to ~/.codex/config.toml:

[mcp_servers.onsense]
command = "uvx"
args = ["onsense", "serve"]

Restart the client once after adding the server. Any other stdio MCP client works the same way — point it at uvx onsense serve.

MCP Tools

These tools are exposed to your AI client after pairing:

If the phone's IP changes, the broker retries using mDNS autodiscovery before surfacing an error.

Clip Bridge (Phone ↔ PC File & Clipboard)

onsense serve automatically starts a clip daemon on port 8770. You can also run it standalone with onsense clip.

Phone → PC push (POST /clip)

The onSense Android app can push content to the PC:

• Images are saved to disk as latest.jpg (in ONSENSE_CLIP_DIR, default <tempdir>/onsense/).
• Text files are saved to disk.
• Other files (video, PDF, etc.) are saved to disk by filename.
• If --set-clipboard is active, images and text are also injected into the PC OS clipboard so you can paste with Ctrl+V immediately.

By default, --set-clipboard is off — files are saved to disk but the clipboard is not touched.

PC → Phone pull (GET /clip)

Off by default. Enable with:

uvx onsense clip --allow-pull

When enabled, the phone can GET /clip to retrieve the current PC clipboard content (copied files first, then images, then text). Returns 204 if the clipboard is empty.

Ports and environment variables

Security

Local network only. The PC-side services bind to all interfaces but reject connections from non-private IP addresses at the application layer. They are not intended to be exposed to the internet.

HMAC request signing. The pairing token is never sent in cleartext. Every authenticated request is signed with HMAC-SHA256 over METHOD\npath\ntimestamp\nnonce\nalgorithm, keyed by a signing key derived from the pairing token via HKDF-SHA256 (a key separate from the encryption key), and carries X-Ts / X-Nonce / X-Sig / X-Enc headers. Servers verify in constant time, reject timestamps outside a ±300 s window, and reject reused nonces — so a sniffed request cannot be replayed and the token cannot be stolen off the wire. New Android installs generate a 128-bit random token, stored on the phone and in ~/.onsense/pair.json (chmod 600) after pairing. (The /health endpoint is unauthenticated.) See PROTOCOL.md for the exact wire format.

Pull and clipboard injection are off by default. GET /clip (phone pulls PC clipboard) and OS clipboard auto-injection (phone push → Ctrl+V) are disabled unless you explicitly pass --allow-pull or --set-clipboard.

Encrypted bodies (AES-256-GCM). Sensitive payloads — camera frames, photos, sensor data, files, and clipboard content — are encrypted between the phone and your PC with AES-256-GCM (no cloud in between, so there is no third party to decrypt them). The key is derived from the pairing token via HKDF-SHA256 (a key separate from the signing key); each message uses a fresh 96-bit nonce, and the GCM tag authenticates the body and binds it to its request (so tampering or response substitution is rejected). A passive sniffer on the same Wi-Fi sees only ciphertext. Low-sensitivity metadata stays plaintext: the open /version and /health endpoints, HTTP error responses, and the saved-file path returned after a push. (Note: large transfers currently buffer the body in memory while encrypting/decrypting — chunked streaming for very large files is a future step. Transport-level TLS is also a possible future hardening.)

File size cap. Incoming pushes are rejected if they exceed ONSENSE_CLIP_MAX_MB (default 200 MB). Set to 0 to remove the cap.

Reporting a vulnerability. Please report security issues privately — see SECURITY.md. Do not open a public issue for security reports.

License

MIT. See LICENSE.

한국어 요약

onsense는 Android 폰(onSense 앱)을 PC AI 에이전트의 카메라·센서로 연결하는 PC측 MCP 브로커입니다.

• uvx onsense pair — 폰과 한 번 페어링하면 Claude Code에 MCP 서버가 자동 등록됩니다. (자동 등록은 Claude Code 전용 — Codex 등 다른 MCP 클라이언트는 각 설정에 uvx onsense serve를 한 번 추가. Codex는 실측 검증됨.)
• uvx onsense doctor — 연결·설치 문제를 진단합니다.
• uvx onsense serve — AI 클라이언트가 호출하는 MCP 서버(stdio)를 실행합니다. 동시에 클립 브리지 데몬(:8770)도 자동 기동합니다.
• uvx onsense clip — 폰↔PC 파일·클립보드 브리지를 단독으로 실행합니다.

폰과 PC는 같은 로컬 Wi-Fi에 있어야 하며, 개발자 운영 클라우드 서버는 없습니다. 전송 계층은 로컬 HTTP지만 민감 본문(카메라·사진·센서·파일·클립보드)은 AES-256-GCM으로 암호화되고 요청은 HMAC 서명됩니다. 다만 메타데이터(버전·오류·저장 경로 등)는 평문이므로 신뢰할 수 있는 네트워크에서 사용하세요.