3DStreet MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to 3DStreet fallback relay from stdio clients to a paired browser tab: Does pairing remain explicit and useful for clients without WebMCP while scene tools match the browser surface?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Drive the signed-in 3DStreet browser editor from an MCP client with live read/write scene tools.

What we know

Local stdio↔WebSocket relay that pairs with one 3DStreet browser tab and forwards the editor's current command registry. The tool surface is dynamic and comes from the connected browser build.

Maintenance / activity evidence

3dstreet-mcp 0.2.3 published 2026-09-03T18:22:24.620Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Broad scene-editor read/write authority. Writes: Create/update/delete/reparent scene entities; Add/remove components/segments; Undo/redo.
Paired browser session.
Sensitive access: Private project/scene data, Signed-in editor session

Direct design-scene mutation; tool surface should be discovered live rather than hard-coded.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does pairing remain explicit and useful for clients without WebMCP while scene tools match the browser surface?

The bounded review of the publisher's documented 3DStreet fallback relay from stdio clients to a paired browser tab and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Direct design-scene mutation; tool surface should be discovered live rather than hard-coded.
Broad scene-editor read/write authority.
Paired browser session.
Scene state is accessed through the paired browser session; relay forwards tools/calls locally.
Reviewed write actions: Create/update/delete/reparent scene entities; Add/remove components/segments; Undo/redo
Sensitive access: Private project/scene data, Signed-in editor session
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
This is the fallback relay for clients without WebMCP, not the browser-embedded service. Pairing a browser tab is required.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Tool list is dynamic and version-dependent.
Requires a signed-in/paired browser tab.
Mutations directly alter the user's 3DStreet scene.
Single-peer relay policy means only one paired tab at a time.

Original activity observations

3dstreet-mcp 0.2.3 published 2026-09-03T18:22:24.620Z

Technical identity

npm/3dstreet-mcp

Exact implementation source: https://www.npmjs.com/package/3dstreet-mcp ↗
Reviewed resource type: MCP Server
Repository identity: 3DStreet/3dstreet-mcp
Package identity: npm:3dstreet-mcp
Service endpoint: paired browser tab at 3dstreet.app

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
3dstreet-mcp
Recorded package identity, distribution or download evidence.
GitHub repository ↗
3dstreet/3dstreet-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
MCP100 setup guide
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · Publisher instructions
npx -y 3dstreet-mcp
reviewed install or registration · Claude Code only · MCP100 composed guide
claude mcp add 3dstreet -- npx -y 3dstreet-mcp
Configure / authenticate
MCP100 setup guide
Requires both MCP stdio registration and a paired 3DStreet browser tab using its localhost WebSocket relay. No vendor credential required for the relay.
Previously reviewed client configuration / prerequisites: official client JSON: command npx, args ["-y","3dstreet-mcp"]. Pairing is separate from stdio registration.
Check connection
Suggested check
Confirm browser tab pairing and MCP tools; stdio launch alone does not establish browser connection.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `3dstreet`, remove the client entry with `claude mcp remove 3dstreet`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove 3dstreet

Official Documentation & Sources

https://www.npmjs.com/package/3dstreet-mcp ↗

What it does

Local stdio↔WebSocket relay that pairs with one 3DStreet browser tab and forwards the editor's current command registry. The tool surface is dynamic and comes from the connected browser build.

Capability: Design & Creative
Resource type: MCP Server
Industry: Real Estate & Construction
Best fit: Drive the signed-in 3DStreet browser editor from an MCP client with live read/write scene tools.

Representative uses

Read scene/entities
Select/focus camera
Create/update/remove/reparent entities
Add/remove components/segments
Undo/redo editor changes

Limitations

Tool list is dynamic and version-dependent.
Requires a signed-in/paired browser tab.
Mutations directly alter the user's 3DStreet scene.
Single-peer relay policy means only one paired tab at a time.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Paired browser session.
Permissions: Broad scene-editor read/write authority.
Data handling: Scene state is accessed through the paired browser session; relay forwards tools/calls locally.
Cost: service_plan
Risk and cautions: Direct design-scene mutation; tool surface should be discovered live rather than hard-coded.

Access scope and cautions

Write actions: Create/update/delete/reparent scene entities Add/remove components/segments Undo/redo
Sensitive access: Private project/scene data Signed-in editor session
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read scene/entities; Select/focus camera; Create/update/remove/reparent entities; Add/remove components/segments; Undo/redo editor changes.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y 3dstreet-mcp. Recorded transport: stdio, local_websocket. Prerequisites: 3DStreet browser/editor session; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No separate API key in the relay; authority comes from the paired signed-in browser session.

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete/reparent scene entities; Add/remove components/segments; Undo/redo. Recorded permission boundary: Broad scene-editor read/write authority.

What data-handling boundary should I consider?

Scene state is accessed through the paired browser session; relay forwards tools/calls locally. Recorded sensitive-access context: Private project/scene data; Signed-in editor session.

What limitations and risks should I check before use?

Direct design-scene mutation; tool surface should be discovered live rather than hard-coded. Tool list is dynamic and version-dependent. Requires a signed-in/paired browser tab. Mutations directly alter the user's 3DStreet scene. Single-peer relay policy means only one paired tab at a time. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use. This is the fallback relay for clients without WebMCP, not the browser-embedded service. Pairing a browser tab is required.

What cost model is recorded?

The reviewed cost model is service plan. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.