Connected in five minutes
A key, a line of config, a sentence. Node.js 20 or newer is the only thing to install.
Issue a key
Sign in and open Account, then Agent keys. The value is shown once and cannot be recovered, only replaced. Give the key a spend cap: that cap is what stands between a looping agent and your balance.
Point your client at the server
One entry in your MCP client's config, with the key in the environment. Claude Desktop and every other MCP client take the same three fields.
Say what you want
"Create a building called Maple Street 14, upload this photo as its view, and start a design with warm grey walls and white trim." A render takes minutes, not seconds. The agent waits and reports back.
The config
Claude Desktop keeps it in claude_desktop_config.json. Paste your key, restart the client, and the tools appear.
{
"mcpServers": {
"getfacade": {
"command": "npx",
"args": ["-y", "@getfacade/mcp"],
"env": { "GETFACADE_API_KEY": "your-key" }
}
}
}Would rather call the API yourself? It is plain HTTP with a bearer key, the same API our own apps use. OpenAPI spec
What the agent can do
Nine tools, and no more than nine: the whole path from a photo to a document a crew can build from.
- Create a building and upload photos of it, waiting while each photo is checked
- Order designs with the same colors and styles the apps offer: real paint and siding products, by brand and code
- Order a cost estimate for the renders you picked
- Order the PDF album: materials, notes, safety and regulatory references, ready to quote from
- Check what is queued, what finished, and what the key has spent
What it cannot do
Left out on purpose, not left for later.
- Buy anything. Credits and plans are bought by a person, on the web.
- Issue or change keys. A key cannot mint another key, so a cap stays a cap.
- Delete your buildings, designs or documents.
Every key carries a hard spend cap and can be revoked in a click, from the same screen that issued it.
Agent access is paid
There are no trial credits in it, and that is a decision rather than an oversight. Every design costs real money to produce, and an agent has neither fatigue nor second thoughts.
- A key works on agent credits, or on an active Pro Plan
- Agent credits are their own balance: the free credits of the app are never spent by a key
- Spending is counted per key, so you can see which assistant spent what
When it refuses
Refusals arrive with their own explanation, and the agent repeats it word for word. None of them is fixed by trying again.
- Out of credits, or no Pro Plan: nothing is spent until the balance is topped up
- Key cap reached: issue a new key or raise the cap, the old one is done
- Photo rejected: send a straight-on daylight shot with the whole house in frame
- Too many requests: the key has its own rate limit, separate from your own sessions
A refused request is refused before any work starts, so a looping agent costs you nothing.
Give your agent a key
Set a cap you are comfortable with, paste it into your client, and ask for the first design.