| FMRS | 36 / 100 · D | 80 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 5 / 20 | 14 / 20 | 13 / 20 |
|---|
| Security and permissions | 6 / 20 | 16 / 20 | 14 / 20 |
|---|
| Maintenance | 12 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 5 / 20 | 15 / 20 | 17 / 20 |
|---|
| Setup experience | 8 / 20 | 18 / 20 | 14 / 20 |
|---|
| Best for | - Developers building automotive 3D/AR apps with the SceneView SDK
- Teams that want AI assistance to quickly prototype car configurators, HUDs, and dashboards
- Automotive visualization projects on Android (Jetpack Compose), iOS (SwiftUI), or Web
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - General-purpose 3D/AR work outside automotive (separate healthcare, gaming, and interior-design servers exist)
- Directly controlling vehicle hardware or safety-critical systems
- Use as a runtime rendering engine—this is a code-assistance MCP server, not a renderer
- Strict production workflows that require a documented tool list and verified client compatibility (the provided material does not include those details)
| - 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)
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - No permissions are documented for this server in the supplied material
- It runs locally as a stdio process via npx, so Node.js and npm are required
- First run requires network access to the npm registry to fetch the automotive-3d-mcp package
- If the AI client writes generated code into a project, it will typically need file-system access per the client's configuration
| - 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
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - AI-generated automotive 3D/AR code may fail to compile or may not match SceneView APIs; human review and testing are required
- Running an npm package via npx executes package code locally; verify the package name, version, and source
- Automotive work can be safety-related, so generated output must never be used directly for vehicle control or safety-critical decisions
- The setup depends on the npm supply chain and network environment; failures may come from network issues, Node versions, or client configuration
| - 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
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Amp |
|---|
| Tools | 0 | 2 | 15 |
|---|