SpatialPack — 3D asset readiness MCP Server

by spatialpack Your server? Claim it

local only

SpatialPack — 3D asset readiness runs on your own machine — the client starts it, so there is no endpoint to ping. 23 installs a week from npm.

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

Installs per day peak 13 · avg 6 · +32% w/w

a month agotoday

Installs / week

npm · @spatialpack/mcp

—

Stars

on GitHub

—

Last commit

0 releases in 90 days

—

License

language unknown

Nothing serious here today

Today is the operative word: we check SpatialPack — 3D asset readiness every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp -- npx -y @spatialpack/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@spatialpack/mcp"
      ],
      "command": "npx"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
command = "npx"
args = ["-y", "@spatialpack/mcp"]

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@spatialpack/mcp"
      ],
      "command": "npx"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@spatialpack/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SPATIALPACK_MCP_SANDBOX (Sandbox root for asset reads and writes, equivalent to --sandbox. Defaults to a per-process temp directory.), SPATIALPACK_MCP_LOG (Log level for the JSON-Lines diagnostic stream on stderr: debug, info, warn, error, or silent. Defaults to info.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to SpatialPack — 3D asset readiness

same job, measured the same way

five46

by sekharsdet

BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success.

57 installs/wk local only

Qarunbook

by ifeanyiejindu

Shared app-testing runbook: read the plan, record results per platform, raise and fix issues.

14 tools answering

SyntheticUser Lab MCP

by syntheticuserlab

Paid remote MCP for synthetic user testing, UX validation, analytics, checkout, and readiness.

answering

fixture.email — Email Testing for Agents

by fixture

Disposable test mailboxes on a real domain: send, receive and assert on real email.

answering

Jarroba Tools · Test audit

by invarato

Audits tests instead of writing them: what each one really asserts. 4 tools, local.

330 installs/wk local only

Whatbreaks Mot

by physics-star-cat

Real UK MOT failure data by car model and mileage, aggregated from official DfT test results.

2 tools answering

TesterArmy

by tester-army

Agents that test your web and mobile app like real users, on every pull request.

answering

Index9

by index9-org

Discover, shortlist, compare, cost-model, and live-test 300+ AI models from your editor

54 installs/wk local only

SpatialPack — 3D asset readiness — questions

Answers built from our own checks of this server.

Why is there no uptime for SpatialPack — 3D asset readiness?

SpatialPack — 3D asset readiness runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @spatialpack/mcp was installed 23 times last week.

How do I connect SpatialPack — 3D asset readiness?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @spatialpack/mcp straight from npm; nothing to host, nothing to sign up for.

How many people use SpatialPack — 3D asset readiness?

The npm package @spatialpack/mcp was installed 23 times in the last week. Week over week that is +32%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.