GetFacade MCP server

@getfacade/mcp

MCP server for GetFacade.ai: an agent creates a building, uploads a photo of it, gets the exterior designed, priced and documented, without a human in front of a screen.

Each design is worked out for the country the building stands in: materials that are applicable there, manufacturer products that are actually sold there, and the technical build-up behind the surface. The render shows that on the photo of the house.

The estimate and the album come from the same design:

in that country.

• The estimate prices it line by line, in materials and labour, at what those materials cost

notes and the norms behind them.

• The album documents it for the crew that builds it: the build-up of the facade, safety

The server is a thin wrapper over the public GetFacade API. It stores nothing, caches nothing and decides nothing: every rule (pricing, admission, the colour grammar, every message) stays on the server, and the wrapper only carries calls and answers.

Requirements

The value is shown once and cannot be recovered; each key carries a hard spend cap.

• Node.js 20+
• An agent API key. Issue one for yourself at app.getfacade.ai → Account → Settings → API.

and without a balance the first paid call is refused with an explanation. An active Pro Plan fills that wallet up to 1,000 credits once per billing period; past that, credits are bought.

• Agent access is paid. There are no trial credits in it: the key spends from the agent wallet,

Setup

Claude Desktop / any MCP client, mcpServers section:

{
  "mcpServers": {
    "getfacade": {
      "command": "npx",
      "args": ["-y", "@getfacade/mcp"],
      "env": { "GETFACADE_API_KEY": "your-key" }
    }
  }
}

To run a checkout instead of the published package, point the client at it: "command": "node", "args": ["/path/to/mcp/src/index.js"].

Messages, including refusals, come from the service in the language of GETFACADE_LANG. Set it to the language the answer should be read in.

Tools

Shortened. The full README is on GitHub.