GetFacade MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to GetFacade photo-bound exterior design and estimate tools: Do country-specific product choices retain source support while renders and estimates share the same design assumptions?

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

Best fit

Facade redesign and estimating from building photos with country-aware materials, product availability and technical assemblies.

What we know

Official agent API/MCP for creating buildings, uploading façade photos, starting/refining designs and ordering estimates/albums. Agent keys can include spending limits that are enforced on paid calls.

Maintenance / activity evidence

@getfacade/mcp 0.2.0 published 2026-10-01T17:13:51.770Z

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.
Project/design/upload plus paid estimate/album generation. Writes: Create projects/buildings; Upload photos; Start/refine design jobs; Order paid estimate/album.
Bearer agent key.
Sensitive access: Property photos, Design/project data, Agent spending key

Can upload private images and spend budget on design/document jobs.

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

All limitations / Review context

Do country-specific product choices retain source support while renders and estimates share the same design assumptions?

The bounded review of the publisher's documented GetFacade photo-bound exterior design and estimate tools 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.

Can upload private images and spend budget on design/document jobs.
Project/design/upload plus paid estimate/album generation.
Bearer agent key.
Building photos/design data are uploaded to GetFacade.
Reviewed write actions: Create projects/buildings; Upload photos; Start/refine design jobs; Order paid estimate/album
Sensitive access: Property photos, Design/project data, Agent spending key
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.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Uploads may contain private property imagery.
Generation/estimate/album operations can incur spend.
Agent key has scoped budget/authority.
Regional material/vendor availability affects outputs.

Original activity observations

@getfacade/mcp 0.2.0 published 2026-10-01T17:13:51.770Z

Technical identity

npm/@getfacade/mcp

Exact implementation source: https://www.npmjs.com/package/@getfacade/mcp ↗
Reviewed resource type: MCP Server
Repository identity: getfacade/mcp
Package identity: npm:@getfacade/mcp
Service endpoint: https://api.getfacade.ai/api/v1

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 ↗
@getfacade/mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
getfacade.ai/zh/agents
Source material retained for this review.
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
Publisher instructions
Hosted OAuth; spending cap during sign-in; paid design calls and optional purchasing-enabled local API keys. Local stdio requires GETFACADE_API_KEY.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add --transport http getfacade https://app.getfacade.ai/mcp
Configure / authenticate
MCP100 setup guide
Prefer publisher hosted HTTP endpoint with sign-in and a spend cap. Local key mode differs; revoke account agent key from GetFacade app when finished. Never test buy_tokens or paid rendering.
Check connection
Suggested check
Inspect the hosted connector OAuth connection or list read-only account/building information. Do not call billed rendering, token purchase, or create/build tools.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `getfacade`, run `claude mcp remove getfacade` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: GetFacade documents app.getfacade.ai → Account → Settings → API, where agent keys are issued; connected agent keys can be revoked in the app. Revoke old key after replacing it; revoked key calls return 401 immediately.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove getfacade

Official Documentation & Sources

What it does

Official agent API/MCP for creating buildings, uploading façade photos, starting/refining designs and ordering estimates/albums. Agent keys can include spending limits that are enforced on paid calls.

Capability: Design & Creative
Resource type: MCP Server
Industry: Real Estate & Construction
Best fit: Facade redesign and estimating from building photos with country-aware materials, product availability and technical assemblies.

Representative uses

Create building/project
Upload façade photo
Start/refine design
Use brand/material selections
Order estimate
Order contractor album/PDF

Limitations

Uploads may contain private property imagery.
Generation/estimate/album operations can incur spend.
Agent key has scoped budget/authority.
Regional material/vendor availability affects outputs.

Reviewed access

Access & risk

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

Authentication: Bearer agent key.
Permissions: Project/design/upload plus paid estimate/album generation.
Data handling: Building photos/design data are uploaded to GetFacade.
Cost: usage_based
Risk and cautions: Can upload private images and spend budget on design/document jobs.

Access scope and cautions

Write actions: Create projects/buildings Upload photos Start/refine design jobs Order paid estimate/album
Sensitive access: Property photos Design/project data Agent spending key
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: Create building/project; Upload façade photo; Start/refine design; Use brand/material selections; Order estimate; Order contractor album/PDF.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @getfacade/mcp. Recorded endpoint: https://api.getfacade.ai/api/v1. Recorded transport: stdio, https_rest. Recorded environment-variable notes: GETFACADE_API_KEY; GETFACADE_API_BASE_URL (optional). No configuration values are supplied here. Prerequisites: Node 20+; GetFacade account/key. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Bearer agent key issued in GetFacade settings; spend cap configured at issuance.

Can it modify data or perform write operations?

Documented write actions include: Create projects/buildings; Upload photos; Start/refine design jobs; Order paid estimate/album. Recorded permission boundary: Project/design/upload plus paid estimate/album generation.

What data-handling boundary should I consider?

Building photos/design data are uploaded to GetFacade. Recorded sensitive-access context: Property photos; Design/project data; Agent spending key.

What limitations and risks should I check before use?

Can upload private images and spend budget on design/document jobs. Uploads may contain private property imagery. Generation/estimate/album operations can incur spend. Agent key has scoped budget/authority. Regional material/vendor availability affects outputs. 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.

What cost model is recorded?

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