Doodleworks MCP vs GetFacade — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Doodleworks MCP vs GetFacade
In-depth architectural comparison of the Doodleworks MCP and GetFacade MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Doodleworks MCP
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
GetFacade
Developer Tools · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Doodleworks MCP if you need specialized Developer Tools tools running via a local process. Choose GetFacade if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Doodleworks MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: OPENAI_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY.
Render a set of single-idea, hand-drawn Tinku illustrations (each 16:9; an optional 21:9 hero) and open an interactive viewer. Supply one entry per illustration; each `prompt` is a contraption composition + Tinku's action + its exact English annotations — the server applies the Tinku character, the conceptual engine, and the house style. Use this when the user wants hand-drawn illustrations for an article, post, or explainer.
get_illustration
Return the rendered image for one illustration of a previously created set. The viewer calls this for each illustration after create_illustrations so a single tool result never carries the whole set.
regenerate_illustration
Re-render a single illustration with the same (or a tweaked) prompt and aspect. Image models are non-deterministic, so this yields a fresh take. Returns the new image in `_meta` for the viewer.
GetFacade Tools (22)
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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Doodleworks MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, GetFacade belongs to Developer Tools using local stdio subprocess. Select Doodleworks MCP when you need capabilities focused on developer tools and GetFacade when you require tools for developer tools.
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.