GetFacade

What the GetFacade MCP server does

The GetFacade MCP server gives an agent access to the public GetFacade API. An agent can create a building, associate one or more photos with it, and request an exterior design rendered onto the original house image. Designs are developed for the building's country, including applicable materials, locally sold manufacturer products, and the technical build-up behind the facade.

The resulting design can support two additional outputs. A cost estimate breaks the work into material and labor lines, with totals and assumptions. A PDF album documents the facade build-up, safety notes, and relevant norms for the crew carrying out the work. Both outputs are based on selected renders from the design.

How it works

The normal workflow starts with create_building, followed by upload_photo or list_photos. The photo can be supplied from a local file when running the package locally, or from an image URL through a remote connection. Photos attached directly to a chat are not readable by the connector; the returned photos_page can be used to add them in the GetFacade app, after which list_photos can find them.

start_design creates a design and returns a job identifier while rendering continues. refine_design applies written changes to a completed design. Use get_job to poll render, estimate, or album jobs, and list_jobs to review recent account activity. Finished render and album links are stable public URLs, so anyone with a link can access them. Deletions are soft on the service and can be undone in the app, but not through this server.

Paid operations use an idempotency key internally. If a connection fails or a request times out, the wrapper retries with the same key so the original job can be recovered instead of creating an accidental duplicate charge.

Setup and configuration

The GetFacade MCP server can be connected remotely at https://app.getfacade.ai/mcp. The account is selected during sign-in, and the connection receives a spend cap. For local use, install or run the npm package with Node.js 20 or newer and provide an agent API key issued from the GetFacade account settings.

The required environment variable is GETFACADE_API_KEY. GETFACADE_API_BASE_URL can override the default API endpoint, and GETFACADE_LANG selects the language returned by the service; its default is English. Agent access is paid, and each key has its own hard spend cap. A key does not automatically purchase tokens unless purchasing was enabled when it was issued.

Tools and capabilities

The GetFacade MCP server exposes tools for:

• Creating, listing, and deleting buildings, designs, renders, and photos.
• Starting and refining designs, upscaling completed renders, and polling asynchronous jobs.
• Ordering albums and line-item estimates, then reading, adding, editing, or deleting estimate lines.
• Checking token packages, wallet balance, and whether the next paid request will be accepted.
• Buying tokens when the key permits local purchases, or returning a checkout URL for human completion.
• Reporting API problems without requiring wallet balance.

Limitations and notes

The wrapper stores and caches nothing; service-side rules, pricing, admission, and responses remain in GetFacade. An agent key can reach the published agent surface—buildings, photos, designs, renders, estimates, albums, jobs, and wallet data—but not account settings, subscriptions, payment history, or key management.

Rendering, refinement, estimates, albums, and upscaling are asynchronous. The first photo upload is the exception: it waits for validation and returns the resulting view, drawing, reference, or refusal. Paid access can be refused when the wallet lacks balance. Public result links do not expire and cannot be revoked through the server, so they should be shared carefully. The GetFacade MCP server is MIT licensed, while use of the underlying service is governed separately by GetFacade's terms.