DisplayXR inline 3D connector
A remote MCP server that helps AI assistants build @displayxr/inline3d web pages that show 3D on Spatial Displays in the DisplayXR Browser, and a 2D fallback everywhere else.
Connect
Server URL (streamable HTTP, no sign-in):
https://mcp.displayxr.org/mcp
- Claude (claude.ai, desktop): Settings → Connectors → Add custom connector → paste the URL.
- Claude Code:
claude mcp add --transport http displayxr-inline3d https://mcp.displayxr.org/mcp - ChatGPT (developer mode): Settings → Apps → Create → paste the URL, authentication: none.
- Codex:
codex mcp add displayxr-inline3d --url https://mcp.displayxr.org/mcp
Tools
get_authoring_guide | The authoring checklist: content type, view rig, depth and comfort, woven-canvas rules, pins, assets. |
scaffold_page | A known-good page template, returned as text. |
check_files | Runs the page checker on the page's own files: a simulated DisplayXR Browser (two real eye views) plus a plain 2D run, pass/warn/fail per rule. |
check_url | The same checker on a deployed page at a public URL. |
get_check_result | Collects a check that was still running. |
check_asset_url | Checks a public .glb/.gltf against a device budget. |
A pass means the page works in a simulated 3D browser; it is not a test on a real 3D display. Checks run on shared capacity with a daily limit; the same checker runs locally for free with npx -y @displayxr/inline3d-tools check.
What happens to your data
Files sent to check_files are served only to the checker's browser and deleted when the check ends. Pages, files and reports are not stored. Your IP address is hashed and kept only as a rate-limit counter for up to a day; request logs are kept at most 7 days. The connector receives no chat history and no account data. Details: privacy · terms.
More
Source · Support · Privacy · Terms · @displayxr/inline3d