AI 에이전트가 사진을 통해 건물 외관을 설계하고, 예상 비용을 산출하며, 기술 문서를 생성할 수 있도록 지원합니다.
다른 이름 getfacade/mcp, mcp, @getfacade/mcp
- 스타
- 1
- Tools
- 22
- 다운로드, 30일
- 354
- 최신 버전
- 0.2.0
- 마지막 커밋
- 2026년 10월 1일
- 라이선스
- MIT
GetFacade MCP란?
AI 에이전트가 사진을 통해 건물 외관을 설계하고, 예상 비용을 산출하며, 기술 문서를 생성할 수 있도록 지원합니다. 22개 도구를 제공합니다. 예: create_building, upload_photo, list_photos.
프로젝트 README에서 생성된 요약
GetFacade MCP server 정보
GetFacade는 AI 에이전트가 건물 외관 설계 및 문서화 작업을 자동화할 수 있는 인터페이스를 제공합니다. 사용자는 기존 구조물의 사진을 리디자인된 파사드로 변환할 수 있으며, 건물이 위치한 국가에 특화된 현지 자재 선택 및 제조사 제품 정보까지 포함할 수 있습니다. 이 MCP server는 GetFacade API를 위한 얇은 래퍼(thin wrapper) 역할을 수행하며, 가격 책정, 컬러 문법 및 기술 규칙에 관한 모든 로직이 서비스 측에서 유지되도록 보장합니다.
개발자는 Claude, ChatGPT 또는 Cursor와 같은 클라이언트에서 사용하기 위해 원격 HTTP URL로 연결하거나, Node.js와 에이전트 API key를 사용하여 로컬에서 실행할 수 있습니다. 시스템은 create_building, upload_photo, start_design과 같은 도구를 통해 복잡한 워크플로우를 관리합니다. 렌더링 및 비용 산출과 같은 비동기 작업은 작업 폴링(job polling) 시스템을 통해 처리됩니다. 또한 멱등성 키(idempotency keys)를 사용하므로, 유료 요청 중 연결이 끊기더라도 실수로 비용이 중복 청구되는 것을 방지합니다.
사용자는 에이전트 지갑을 통해 비용을 관리하고 특정 지출 한도를 설정할 수 있습니다. 서버는 상세한 항목별 견적과 시공팀을 위한 기술 PDF 앨범에 대한 접근 권한을 제공하며, 완료된 렌더링 결과물에 대해서는 영구적인 공개 링크를 생성합니다.
활용 사례
- 1현지화된 비용 산출개발자는 건물의 위치에 특화된 자재 및 인건비의 상세 내역을 요청할 수 있습니다.
- 2기술 시공 문서 생성에이전트는 시공팀을 위해 안전 주의 사항과 기술적 시공 상세 정보가 포함된 PDF 앨범을 생성할 수 있습니다.
- 3반복적인 디자인 개선사용자는 자연어를 사용하여 기존 건축 디자인을 수정할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
GetFacade MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 GetFacade MCP 설치
$ claude mcp add --env 'GETFACADE_API_KEY=<YOUR_GETFACADE_API_KEY>' mcp -- npx -y @getfacade/mcpCursor에 GetFacade MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@getfacade/mcp"
],
"env": {
"GETFACADE_API_KEY": "<YOUR_GETFACADE_API_KEY>"
}
}
}
}VS Code에 GetFacade MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@getfacade/mcp"
],
"env": {
"GETFACADE_API_KEY": "<YOUR_GETFACADE_API_KEY>"
}
}
}
}VS Code CLI에 GetFacade MCP 설치
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@getfacade/mcp"],"env":{"GETFACADE_API_KEY":"<YOUR_GETFACADE_API_KEY>"}}'Claude Desktop에 GetFacade MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@getfacade/mcp"
],
"env": {
"GETFACADE_API_KEY": "<YOUR_GETFACADE_API_KEY>"
}
}
}
}Codex에 GetFacade MCP 설치
$ codex mcp add mcp --env 'GETFACADE_API_KEY=<YOUR_GETFACADE_API_KEY>' -- npx -y @getfacade/mcpCodex config.toml에 GetFacade MCP 설치
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@getfacade/mcp"] [mcp_servers.mcp.env] GETFACADE_API_KEY = "<YOUR_GETFACADE_API_KEY>"
Gemini CLI에 GetFacade MCP 설치
$ gemini mcp add -s user -e 'GETFACADE_API_KEY=<YOUR_GETFACADE_API_KEY>' mcp npx -- -y @getfacade/mcpGemini settings.json에 GetFacade MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@getfacade/mcp"
],
"env": {
"GETFACADE_API_KEY": "<YOUR_GETFACADE_API_KEY>"
}
}
}
}GetFacade MCP 도구 22
README에서 감지됨create_buildingupload_photolist_photosstart_designrefine_designget_joblist_jobslist_designsorder_estimateorder_albumupscale_renderget_estimate
| create_building | — | |
| upload_photo | — | |
| list_photos | — | |
| start_design | — | |
| refine_design | — | |
| get_job | — | |
| list_jobs | — | |
| list_designs | — | |
| order_estimate | — | |
| order_album | — | |
| upscale_render | — | |
| get_estimate | — |
도구 22개 모두 보기도구 수 줄이기
add_estimate_lineupdate_estimate_linedelete_estimate_linedelete_renderdelete_designdelete_buildinglist_token_packagesbuy_tokensget_balancereport_problem
| add_estimate_line | — | |
| update_estimate_line | — | |
| delete_estimate_line | — | |
| delete_render | — | |
| delete_design | — | |
| delete_building | — | |
| list_token_packages | — | |
| buy_tokens | — | |
| get_balance | — | |
| report_problem | — |
구성
GETFACADE_API_KEY필수비밀Agent key issued at app.getfacade.ai under Account, Settings, API. Shown once.
GETFACADE_API_BASE_URLBase URL of the API. Leave unset to use the production one.
GETFACADE_LANGLanguage the service answers and refuses in. Leave unset for English.
| 이름 | 설명 | 유형 |
|---|---|---|
| GETFACADE_API_KEY | Agent key issued at app.getfacade.ai under Account, Settings, API. Shown once. | 필수비밀 |
| GETFACADE_API_BASE_URL | Base URL of the API. Leave unset to use the production one. | |
| GETFACADE_LANG | Language the service answers and refuses in. Leave unset for English. |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능getfacade/mcp is public and reachablegithub.com/getfacade/mcp ↗통과
- 패키지가 이 저장소를 소스로 명시@getfacade/mcp names getfacade/mcp as sourcenpmjs.com/package/@getfacade/mcp ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for @getfacade/mcpnpmjs.com/package/@getfacade/mcp/v/0.2.0#provenance ↗통과
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-01github.com/getfacade/mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @getfacade/mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음99 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음22 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기@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:
- The estimate prices it line by line, in materials and labour, at what those materials cost in that country.
- The album documents it for the crew that builds it: the build-up of the facade, safety notes and the norms behind them.
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.
Connect by URL
Most clients connect without installing anything. Add a custom connector with this URL and sign in to your GetFacade account when asked:
https://app.getfacade.ai/mcp
- Claude (claude.ai and desktop): Settings → Connectors → Add custom connector.
- Claude Code:
claude mcp add --transport http getfacade https://app.getfacade.ai/mcp - ChatGPT, Cursor, VS Code and other MCP clients: add a remote (HTTP) server with the same URL.
On the sign-in screen you set a spend cap for the connection. It spends tokens from the agent wallet of your account and never buys tokens on its own. The connection appears among your agent keys in the app, where it can be revoked at any time.
A photo attached to a chat has no link the connector can read. create_building returns
photos_page, the building's photo page in the app: add the photo there, and list_photos picks
it up. A direct public link to an image works with upload_photo as well.
Run locally
The package below runs the same tools on your own machine with an agent key. Use it for automation, or when the photos are files on that machine.
Requirements
- Node.js 20+
- An agent API key. Issue one for yourself at app.getfacade.ai → Account → Settings → API. The value is shown once and cannot be recovered; each key carries a hard spend cap.
- Agent access is paid. There are no trial credits in it: the key spends from the agent wallet, 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.
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"].
| Variable | Required | Default |
|---|---|---|
GETFACADE_API_KEY |
yes | — |
GETFACADE_API_BASE_URL |
no | https://api.getfacade.ai/api/v1 |
GETFACADE_LANG |
no | en |
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
| Tool | What it does |
|---|---|
create_building |
Creates a building. The name is unique per account. Say where it stands, or the place is inferred from the connection the call arrives on. |
upload_photo |
Takes a file path (local) or an image link (URL connection). Registers the file, uploads the bytes, confirms, waits for the answer: a view to design from, a drawing or reference kept with the building, or a refusal with the reason. |
list_photos |
The views of a building, including photos added in the app. view_id is what start_design takes. |
start_design |
Creates a design and queues its render. Returns a job id. |
refine_design |
Changes a finished design in words. Every step after the first. |
get_job |
Polls one render, estimate or album. |
list_jobs |
Recent jobs across the account, unfinished first. |
list_designs |
Designs of a building with their renders and finished picture. |
order_estimate |
Orders a cost estimate for chosen renders. |
order_album |
Orders the PDF album for chosen renders. |
upscale_render |
Enlarges a finished render. Costs tokens, asynchronous. |
get_estimate |
The estimate itself: totals, assumptions and every line. |
add_estimate_line |
Adds one line to an estimate. |
update_estimate_line |
Edits one line of an estimate. |
delete_estimate_line |
Removes one line from an estimate. |
delete_render |
Deletes one render. The main render's design returns to draft. |
delete_design |
Deletes one design with the renders under it. |
delete_building |
Deletes a building with everything under it. |
list_token_packages |
The packages this account can buy. |
buy_tokens |
Refills this key's wallet. Local package only. See below. |
get_balance |
Agent wallet, key cap, and whether the next paid call will be accepted. |
report_problem |
Reports a defect in this API. Free, and works on an empty wallet. |
Rendering is asynchronous: start_design, refine_design, order_estimate and order_album return a job id
immediately, and get_job reports when it is done. A finished estimate reads ready where a
render and an album read completed. The only call that waits is upload_photo, which polls
until the answer is in.
A paid call is never ordered twice
start_design, refine_design, order_estimate, order_album and upscale_render cost
money, and the charge follows the job that gets created. If one of them times out, the honest
question is whether the job exists, and the agent cannot answer it from where it stands.
So this server answers it instead. Every paid call goes out under a name of its own
(Idempotency-Key), and this server, not the agent, retries it under that same name when the
connection fails or when the API says the first attempt is still running. The API recognises
the repeat and hands back the original job, so a timeout costs one design, not two.
Nothing about this reaches the tool arguments: ordering the same design twice on purpose stays possible, because two calls are two names. What is gone is the accidental second order.
The API requires that name on every paid call made with an API key, so calling it without this wrapper means sending the header yourself. The reference is at getfacade.ai/agents.
What the key can reach
A key is a bearer secret that lives in your agent's config, so its reach is the published agent
surface and nothing else: buildings, photos, designs, renders, estimates, albums, the jobs list
and the API wallet. Anything outside that answers 403 AGENT_SURFACE_FORBIDDEN, including the
account's own sign-in settings, its subscription and its payment history. Changing those, and
issuing or revoking keys, is done by a person signed in to the app.
The reference is at getfacade.ai/agents.
Results are permanent public links
A finished render (result_url, main_render_url) and a finished album (result_url) are
served from stable URLs: no signature, no expiry. An assistant can hand one straight to a
person as the answer to "show me the result", with nothing to refresh and no second call.
The honest half of that: because the link is unsigned it asks nobody for permission, so it
keeps working for whoever it is forwarded to, and it cannot be recalled afterwards. Share it as
deliberately as any other link that is public forever. GET /renders/{render}/download is a
different thing — a short-lived signed URL with a filename, for saving the file rather than for
sharing it.
Deletions are soft on the server: a person can undo them in the app, this server cannot.
buy_tokens works only if the key was issued with purchasing enabled (a switch on the
issue screen), and only up to what the key may still spend — a purchase never lifts the key's
own spend cap. It answers charged when the payment provider took it from a saved payment
method, or requires_human with a checkout_url for a person to open. Either way the tokens
are credited when the payment is confirmed, so poll get_balance.
Issuing keys and buying a subscription are deliberately absent: a key that can issue itself a key has no ceiling, and a subscription is bought by a person, in the app.
License
MIT (see LICENSE) — this wrapper carries calls and answers and nothing else, so there is
nothing in it to keep closed. The GetFacade service it talks to is a separate matter: using it
is governed by the terms at getfacade.ai/terms, and a key is
issued to an account, not to this package.
Development
npm install
npm test # smoke test against a stub of the API
test/live-journey.mjs drives the whole journey through a real MCP client against a real API
with a real key. It is not part of npm test, because it spends actual credits; the header of
the file says how to run it.
Releases: see RELEASING.md.
GetFacade MCP 질문
GetFacade MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'GETFACADE_API_KEY=<YOUR_GETFACADE_API_KEY>' mcp -- npx -y @getfacade/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
GetFacade MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
GetFacade MCP는 어떤 도구를 제공하나요?
22개 도구를 제공합니다. 예: create_building, upload_photo, list_photos, start_design, refine_design.
GetFacade에 어떻게 연결하나요?
Claude 또는 ChatGPT와 같은 클라이언트에서 커스텀 URL을 통해 연결하거나, 에이전트 API key를 사용하여 로컬에서 실행할 수 있습니다.
채팅창에 사진을 직접 올려서 사용할 수 있나요?
채팅에 직접 첨부한 사진은 커넥터가 읽을 수 없습니다. 도구를 통해 사진을 업로드하거나 앱 내 건물의 사진 페이지에 추가해야 합니다.