
CCPhoto — Phone Camera Bridge
io.github.stepankaiserPublished by GitHub account stepankaiserv0.3.1Updated Oct 24, 2026
Phone camera bridge for Claude Code — photos, live video, voice, and generative UI
Overview
Bridges a phone camera to Claude Code over the local network so the assistant can capture photos, stream video, and display content on the phone.
- What you can do
- CCPhoto runs a local MCP server that shows a QR code; scanning it opens a camera page in the phone's browser, and photos are sent back to Claude. Tools include capture_photo, wait_for_photo, get_latest_photo, list_photos, send_to_phone, start_livestream, and get_live_frame. It also supports annotated photos, voice input with spoken replies, and generative UI panels rendered on the phone.
- When to use it
- Useful when you want Claude to see physical objects, whiteboards, labels, or circuit boards through your phone camera, or to use the phone as a second screen for instructions and diagrams. It suits hands-free or two-handed work where a webcam is impractical.
- Requirements
- Runs as a local Node.js process, typically via npx ccphoto or a global npm install. The computer and phone must be on the same local network, and the phone needs a browser with camera access. Live video requires HTTPS. An optional CCPHOTO_DIR environment variable overrides the photo storage directory.
Installation
In SourceWeft
- Open CCPhoto — Phone Camera Bridge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
CCPhoto
[npm version] [License: MIT] [Node.js]
Bridge your phone camera to Claude Code over the local network.
CCPhoto is an MCP server that lets you take photos on your phone and send them directly to Claude Code. Point your phone at a circuit board, a whiteboard, a label -- anything -- and Claude sees it instantly. No app install required; your phone's browser camera does all the work.
Quick Start
Then in Claude Code, just say "take a photo" -- Claude handles the rest.
How It Works
- Claude calls the
capture_photoMCP tool. - A QR code appears in your terminal.
- Scan it with your phone -- a camera page opens in your browser.
- Take a photo -- Claude receives the image directly.
No app install needed. The phone's native camera is accessed through the
<input capture> HTML attribute.
Always-On Mode
The server starts on the first capture_photo call and stays running for the
entire session. Your phone stays connected -- there is no need to re-scan the
QR code. Take as many photos as you like, and retrieve any of them by asking
Claude.
Photo Request Notifications
When your phone is already connected and Claude calls capture_photo again, the
phone receives an SSE push notification. The capture button pulses to let you
know Claude is waiting for a new photo. Just tap and shoot.
Bidirectional Messaging
Claude can send content to your phone using the send_to_phone tool. Text, markdown,
and images appear in a collapsible panel on the phone. This turns your phone into a
reference screen -- Claude can display wiring instructions, pinout diagrams, or code
snippets while you work with both hands.
Photo Annotations
After taking a photo, an annotation screen appears where you can draw on the image before sending it. Use colored pens (red, blue, green, white) to circle components, draw arrows, or highlight areas of interest. Tap "Send" to upload the annotated image, or "Skip" to send the original photo without annotations.
Live Video Assistant
Start a semi-real-time video stream from your phone camera. Claude watches the live feed (one frame every 3 seconds) and provides guidance in real-time -- point the camera where Claude asks, and receive instructions on your phone screen.
Requires HTTPS (for camera access). On Android Chrome, accept the certificate warning once. Currently Android/Chrome only; iOS support planned.
Voice Interaction
Tap the microphone button on your phone to speak to Claude. Speech is
transcribed using the browser's built-in Speech Recognition API and sent as
text. Claude can respond with spoken audio using send_to_phone with
speak: true -- the phone speaks the response aloud via Text-to-Speech.
This enables hands-free workflows: ask a question while holding a soldering iron, and hear the answer without looking at a screen. The mic button appears only on browsers that support Speech Recognition (Android Chrome).
Generative UI
Claude can generate rich, contextual UI on your phone based on what it sees. Point your camera at a product, component, recipe, or anything -- Claude analyzes it and sends a custom interactive interface to your phone display.
12 component types: Card, Text, Image, Metric, MetricGrid, Checklist, StepByStep, Alert, Table, Timer, Badge, and Divider. Claude composes these into contextual layouts -- a plant care card with watering checklist, a circuit component table with pin diagrams, or a step-by-step repair guide with timers.
Use send_to_phone with the ui_spec parameter to generate custom UI.
Installation
npx (recommended, no install)
Global install
From source
If you prefer to register the MCP server manually instead of using --setup:
MCP Tools Reference
Standalone CLI Mode
CCPhoto can also run independently, without Claude Code:
A QR code is printed to the terminal. Scan it, take photos, and they are saved to disk. The server stays running for multiple captures.
CLI Options
Configuration
Security
- Session token -- A cryptographically random 32-character hex token is generated for each server session. Every request must include the token.
- Timing-safe comparison -- Token validation uses
crypto.timingSafeEqualto prevent timing attacks. - Local network only -- The server binds to your local network IP. No data leaves your network.
- No external services -- Photos are transferred directly between your phone and the server over HTTP on your LAN. Nothing is uploaded to the cloud.
Troubleshooting
Could not detect local network IP
Make sure your computer is connected to WiFi (not just Ethernet in some configurations). CCPhoto needs a LAN IP address that your phone can reach.
QR code does not scan
Try increasing your terminal font size or reducing the terminal width so the QR code renders at a scannable resolution. You can also copy the URL printed below the QR code and type it into your phone's browser manually.
Phone camera does not open
The camera capture feature requires HTTPS on some browsers, but most mobile browsers allow it on plain HTTP for local network addresses. If your browser blocks camera access, try using Safari (iOS) or Chrome (Android).
Upload fails
Verify that your phone and computer are on the same WiFi network. Corporate networks with client isolation may block device-to-device traffic. Try a personal hotspot or home network instead.
Development
Tests use the Node.js built-in test runner and require the tsx dev dependency
for TypeScript execution.
Project structure:
Roadmap
- Real domain + Let's Encrypt certs -- Use a registered domain with valid certificates for zero browser warnings on any device, including iOS Safari.
- iOS live video support -- Live video streaming currently works on Android/Chrome. iOS Safari support requires trusted certificates.
- AR overlays on camera feed -- Draw annotations directly on the live camera view in real-time.
- Multi-camera support -- Connect multiple phones simultaneously for different viewing angles.
- WebRTC streaming -- Replace HTTP frame polling with WebRTC when Claude's vision processing latency improves.
Contributing
Contributions are welcome.
- Fork the repository
- Create a feature branch (
git checkout -b my-feature) - Make your changes
- Run
npm testto verify nothing is broken - Commit your changes (
git commit -m "Add my feature") - Push to your branch (
git push origin my-feature) - Open a pull request
When reporting a bug, please include your Node.js version, OS, and the steps to reproduce the issue.
License
Source: README.md at commit 6e5eeef
Tools
0Version history
1- v0.3.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts