MCP server for GetFacade.ai: design a house exterior on its own photo, with materials that apply in the building's country, products really sold there, and the build-up behind the surface
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
GETFACADE_API_KEYAPI keyrequiredAgent key issued at app.getfacade.ai under Account, Settings, API. Shown once.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
create_buildingCreate a building (a house to design). The name must be unique within the account, max 50 characters — reusing a name is refused, so pick a distinct one instead of retrying the same. `goals` is the free-form brief (max 10000 chars).Create a building (a house to design). The name must be unique within the account, max 50 characters — reusing a name is refused, so pick a distinct one instead of retrying the same. `goals` is the free-form brief (max 10000 chars).
No input schema was published for this tool.
upload_photoprivilegedNo description publishedThis tool published no description. Forge does not invent one.
start_designNo description publishedThis tool published no description. Forge does not invent one.
refine_designNo description publishedThis tool published no description. Forge does not invent one.
get_jobNo description publishedThis tool published no description. Forge does not invent one.
list_jobsRecent jobs across the account — renders, estimates and albums in one list, unfinished ones first. Use it to catch up after a restart: each row carries the `kind` and `design_id` that get_job asks for, and the `building_id` the job belongs to. Use get_job to poll a single known job.Recent jobs across the account — renders, estimates and albums in one list, unfinished ones first. Use it to catch up after a restart: each row carries the `kind` and `design_id` that get_job asks for, and the `building_id` the job belongs to. Use get_job to poll a single known job.
No input schema was published for this tool.
list_designsAll designs of a building with their renders. This is where the render ids for order_estimate, order_album and refine_design come from — `main_render_id` is the finished render of a design, null while nothing has finished, and `main_render_url` is its permanent public link (no signature, no expiry,…All designs of a building with their renders. This is where the render ids for order_estimate, order_album and refine_design come from — `main_render_id` is the finished render of a design, null while nothing has finished, and `main_render_url` is its permanent public link (no signature, no expiry,…
No input schema was published for this tool.
order_estimateNo description publishedThis tool published no description. Forge does not invent one.
order_albumNo description publishedThis tool published no description. Forge does not invent one.
upscale_renderEnlarge a completed render to a higher resolution. Costs tokens like a render and runs asynchronously: poll the returned job with get_job. A render that is already upscaled, or not finished yet, is refused by the API with an explanation.Enlarge a completed render to a higher resolution. Costs tokens like a render and runs asynchronously: poll the returned job with get_job. A render that is already upscaled, or not finished yet, is refused by the API with an explanation.
No input schema was published for this tool.
get_estimateThe finished estimate: its totals, the area and duration it assumes, and every line with its quantity, unit and price. This is the only way to see what was estimated — get_job reports the status of an estimate, never its content. The `unit` of a line is the display code to reuse in add_estimate_lin…The finished estimate: its totals, the area and duration it assumes, and every line with its quantity, unit and price. This is the only way to see what was estimated — get_job reports the status of an estimate, never its content. The `unit` of a line is the display code to reuse in add_estimate_lin…
No input schema was published for this tool.
add_estimate_lineAdd one line to a generated estimate. `unit` must be a display code of the estimate's own measurement system — read an existing line to see which codes it uses rather than guessing. Totals are recomputed by the server.Add one line to a generated estimate. `unit` must be a display code of the estimate's own measurement system — read an existing line to see which codes it uses rather than guessing. Totals are recomputed by the server.
No input schema was published for this tool.
update_estimate_lineChange one line of a generated estimate — its name, quantity, unit, unit price, category or section. Only the fields passed are changed. Totals are recomputed by the server.Change one line of a generated estimate — its name, quantity, unit, unit price, category or section. Only the fields passed are changed. Totals are recomputed by the server.
No input schema was published for this tool.
delete_estimate_lineprivilegedRemove one line from a generated estimate. Totals are recomputed by the server.Remove one line from a generated estimate. Totals are recomputed by the server.
No input schema was published for this tool.
delete_renderprivilegedDelete one render. Deleting the main render of a design returns that design to draft, so it can be rendered again without creating a new one. Deletion is soft on the server side and can be undone by a person in the app; this tool cannot undo it.Delete one render. Deleting the main render of a design returns that design to draft, so it can be rendered again without creating a new one. Deletion is soft on the server side and can be undone by a person in the app; this tool cannot undo it.
No input schema was published for this tool.
delete_designprivilegedDelete one design (concept) of a building, with the renders under it. Deletion is soft on the server side and can be undone by a person in the app; this tool cannot undo it.Delete one design (concept) of a building, with the renders under it. Deletion is soft on the server side and can be undone by a person in the app; this tool cannot undo it.
No input schema was published for this tool.
delete_buildingprivilegedDelete a building with everything under it: photos, designs, renders, estimates and albums. Deletion is soft on the server side and can be undone by a person in the app; this tool cannot undo it. Tokens already spent are not refunded.Delete a building with everything under it: photos, designs, renders, estimates and albums. Deletion is soft on the server side and can be undone by a person in the app; this tool cannot undo it. Tokens already spent are not refunded.
No input schema was published for this tool.
list_token_packagesThe packages this account can buy, with their price and how many tokens each carries. Read this before buy_tokens instead of assuming a ladder — the packages and their prices change.The packages this account can buy, with their price and how many tokens each carries. Read this before buy_tokens instead of assuming a ladder — the packages and their prices change.
No input schema was published for this tool.
buy_tokensNo description publishedThis tool published no description. Forge does not invent one.
get_balanceWhat this key can still spend: the api-scope balance of the account and the cap of this key. `is_admissible` is the server's own answer to "will the next paid call be accepted" — read it instead of comparing the numbers yourself.What this key can still spend: the api-scope balance of the account and the cap of this key. `is_admissible` is the server's own answer to "will the next paid call be accepted" — read it instead of comparing the numbers yourself.
No input schema was published for this tool.
report_problemNo description publishedThis tool published no description. Forge does not invent one.
13 of 21 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for GetFacade.ai: design a house exterior on its own photo, with materials that apply in the building's country, products really sold there, and the build-up behind the surface
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.