Sceneview MCP Server

3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation. Exposed over MCP by the sceneview mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Build 3D and AR experiences with the UI frameworks you already know. Same concepts, same simplicity — Android, iOS, Web, Desktop, TV, Flutter, React Native.

Its toolset

Everything the assistant can do here goes through one of these:

• Cross — platform reminder hooks** — gentle nudges when you edit Android, iOS, Web, or KMP-core APIs to keep the other platforms in sync

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Sceneview's toolset — Cross — is a fair guide to whether it matches your workflow. It is maintained by ThomasGorisse; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Sceneview's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the sceneview mcp server does with a few real requests.