Labsco
MCP SERVER · OFFICIAL PROJECT

SceneView MCP

by sceneview

SceneView's setup guides, samples, API reference and a code validator — so an assistant's 3D and AR code compiles the first time.

Framework & SDK Documentation LookupVerified
Summary
A validator between the model and your build is what changes the hit rate.

Samples and an API reference help, but validate_code is the piece that catches the classic failure — an assistant confidently importing a node type that does not exist — by checking symbols against the real public API and pointing at the nearest real one. analyze_project runs the same idea backwards over code you already have, reporting the version it is pinned to and the anti-patterns sitting in it.

What it is

The official server for SceneView, the cross-platform 3D and AR SDK for Android, iOS and the web. It carries the setup guides, compilable samples and API reference, checks generated code against the real public API, and can go find or generate the 3D assets that code refers to.

What you get
  • Setup for whichever platform you are on — Gradle and manifest for Android, SPM and Info.plist for iOS, Kotlin/JS and Filament.js for the web, and AR permissions with ARCore session options — get_platform_setup, get_setup, get_ios_setup, get_web_setup, get_ar_setup
  • Compilable samples browsed by tag and returned whole — list_samples, get_sample
  • The exact signature, parameters and usage example for a node type or composable — get_node_reference
  • Kotlin and Swift snippets checked against the real public API: unknown imports, invented node types, threading violations and wrong destroy order, with did-you-mean suggestions — validate_code
  • 2.x code migrated automatically, and the migration guide with before-and-after for every breaking change — migrate_code, get_migration_guide
  • Topic guides for animation, gestures, materials, collisions, performance and model optimization, plus web rendering and general best practices
  • Debugging by symptom — model not showing, AR not working, crash, black screen, build error — get_troubleshooting, debug_issue
  • A project on disk scanned for platform, SceneView version, whether it is behind, and the anti-patterns already in the source — analyze_project
  • Free 3D models found on Sketchfab with author, licence and triangle count, or a new GLB generated from a prompt or an image — search_models, generate_3d_model
  • Google's Android documentation searched and fetched, for the moments the answer is a stock Android API rather than a SceneView one — search_android_docs, fetch_android_doc
  • Which platforms are supported today and what is planned — list_platforms, get_platform_roadmap
  • Three tools marked [PRO]: a shareable interactive preview link, a self-contained HTML artifact, and a scene generated from a written description — render_3d_preview, create_3d_artifact, generate_scene
Requirements

The developer tools need no account: npx sceneview-mcp runs it over stdio on Node 18 or newer, and the documentation and samples are bundled. Model search uses your own Sketchfab token in SKETCHFAB_API_KEY and model generation your own Tripo AI key in TRIPO_API_KEY; without them everything else still works, since the only outbound calls are to GitHub, Sketchfab and Tripo. The Android documentation tools need Google's android CLI on the host's PATH. Telemetry covering client and tool names is on by default and switches off with SCENEVIEW_TELEMETRY=0.

Setup effort

One command — npx sceneview-mcp