SpatialPack — 3D asset readiness

dev.spatialpackPublished by spatialpack.devv0.1.0Updated Oct 24, 2026

Test whether 3D assets survive Apple Quick Look and Safari <model>, then fix what fails

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

Checks whether 3D assets render correctly in Apple Quick Look and Safari's model element, and helps fix assets that fail.

What you can do
SpatialPack is a local MCP server that tests 3D asset readiness for Apple Quick Look and Safari's model element. It reports which assets survive those viewers and helps fix the ones that fail. It runs as a local process over stdio, so the assistant invokes it on the user's machine.
When to use it
Use it when preparing 3D assets for Apple platforms and you want an assistant to verify they display correctly in Quick Look or Safari before shipping. It is aimed at asset pipelines where viewer compatibility matters.
Requirements
Runs locally via npx from the npm package @spatialpack/mcp over stdio. Desktop only; no web executable. Optional environment variables: SPATIALPACK_MCP_LOG for log level and SPATIALPACK_MCP_SANDBOX for the sandbox root for asset reads and writes. No authentication declared.
Before you install
The server reads and writes assets within a sandbox root; by default that is a per-process temp directory, so point SPATIALPACK_MCP_SANDBOX at a directory you are comfortable having modified. No credentials or payments are involved.

Installation

In SourceWeft

  1. Open SpatialPack — 3D asset readiness in the dashboard and add it to a workspace.
  2. 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.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

15% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.