Credentials. The sign-in stores a revocable API key on your machine, so keep that key private.
Reverse engineering. Scans of private rooms are uploaded to the hosted service unless you self-host, so check that you are comfortable with that before uploading.
Who it is forA homeowner, renter, or designer who needs quick answers about a physical room without walking around with a tape measure.
The problemDescribing a room to an AI assistant from memory or photos gives vague answers about what is there and how large it is.
The outcomeA persistent 3D scene of the room that the assistant can query for objects and room size.
What you need first
- Node.js and npx, so the openreality-mcp package can run
- An MCP-capable AI assistant such as Claude Code, Codex, Cursor, or Claude desktop
- A phone video of the space you want to scan
- A browser to complete the one-time sign-in (hosted service)
Steps
- Add the tools to your assistant:
claude mcp add openreality -- npx -y openreality-mcp serve(orcodex mcp add openreality -- npx -y openreality-mcp serve). - Sign in once with
npx -y openreality-mcp login. - Record a video of the room on your phone, or upload a file such as ~/Videos/kitchen.mp4 by asking your assistant to upload it.
- Wait for the reconstruction to finish. The README says this takes a few minutes.
- Ask: "What objects are in my latest scan, and how big is the room?"
Prompt for your agent
In the openreality repo's MCP tools, upload <video path>, reconstruct it, then list the objects in the resulting scene and report the room size. Verify that the answer says whether dimensions are metric or relative, because the README states numbers are only called metres after calibration.
Caveat. Numbers stay relative until you calibrate the scene with a known real distance, so do not treat room size as metres before that step.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page