| FMRS | 13 / 100 · D | 80 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 2 / 20 | 14 / 20 | 12 / 20 |
|---|
| Security and permissions | 2 / 20 | 16 / 20 | 16 / 20 |
|---|
| Maintenance | 3 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 2 / 20 | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 4 / 20 | 18 / 20 | 15 / 20 |
|---|
| Best for | - Developers building SceneView-based 3D/AR interior-design features
- Teams that want AI-assisted generation of room planners, furniture configurators, and lighting previews
- MCP workflows already using Claude Code, Claude Desktop, Cursor, or Windsurf
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - General-purpose 3D or AR development — use the main sceneview MCP server (28 tools) instead
- Other verticals such as automotive, healthcare, gaming, or Rerun.io debugging (separate specialty servers)
- Projects that need exact, pre-documented tool names — the sources do not list this server's 7 tool names
- Scenarios where other 5 MCP servers in the same repo would be confused with this one
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Runs as a local child process via npx, so it inherits the permissions of the launching client or shell (the README describes no restricted permission model)
- May need read/write access to files in the current project if generate/analyze-style tools are invoked
- Network access is required to download the npm package and potentially SceneView assets
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Running `npx` executes third-party code on your machine; pin versions and review the package before use
- This server is maintained as part of the SceneView repository and is not an official Anthropic MCP server; verify its maintenance status
- AI-generated SceneView code may require a matching SDK version (e.g. 4.26.0) and platform-specific setup (Android/Filament, iOS/RealityKit, Web) to compile
- Because tool names are undocumented in the supplied material, tool calls may fail if the client expects specific identifiers
- Easy to confuse with the other 5 MCP servers in the repo — this profile covers only interior-design-3d
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor, Windsurf | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 0 | 2 | 19 |
|---|