Head to head · Design code · October 2026 research run
Impeccable vs Penpot API + MCP
Impeccable scores 69.6 (B) on agent readiness against Penpot API + MCP's 43.7 (E), and leads in every scored category. Both do design code.
Best design workspace and canvas APIs for AI agents · All 73 design comparisons
Which one, for what
Best for Coding agents building or reviewing web interfaces that need a design vocabulary and a deterministic check for AI-generated UI patterns, contrast and design-system drift, in a terminal, CI job or the agent's own hooks.
Ahead on
- Reliability, 85 against 46
- Schema & documentation, 78 against 66
- Agent ergonomics, 66 against 41
- Security & auth, 50 against 33
- Payments & pricing, 60 against 30
Also in its favour
- No key needed to call it
- No incidents deducted, where Penpot API + MCP loses 5 points for them
Watch for
No JSON Schema for the findings; their shape is defined in a 610 KB contract document
Best for Teams that want design files on their own servers and an agent working alongside a person in the editor.
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
Personal access tokens have no scopes, and the hosted MCP key goes in a URL query string
Score by category
| Category | Weight this run | Impeccable | Penpot API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 85 | 46 | Impeccable +39 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 78 | 66 | Impeccable +12 |
| Agent ergonomics | 13%16.2 | 66 | 41 | Impeccable +25 |
| Security & auth | 14%17.5 | 50 | 33 | Impeccable +17 |
| Payments & pricing | 10%12.5 | 60 | 30 | Impeccable +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 79 | 76 | Impeccable +3 |
| Transparency & trust | 7%8.8 | 69 | 68 | Impeccable +1 |
| Negative events | ≤15 | 0 | -5 | |
| Total | B 69.6/100 | E 43.7/100 |
Facts side by side
| Fact | Impeccable | Penpot API + MCP |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Renaissance Geek, Inc. | Penpot (Kaleidos) |
| Hosted endpoint | no (local only) | https://design.penpot.app/api/rpc/command |
| Transports | HTTP, Streamable HTTP | |
| Auth | None | Token |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0. NOTICE.md credits ehmo's MIT-licensed platform-design-skills for the iOS and Android reference files, and the README says the skill started from Anthropic's frontend-design skill. | MPL-2.0 |
| Tools exposed | none | 5 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-26 | 2026-10-01 |
| Terms last updated | no date given | 2025-08-05 |
| Privacy policy last updated | 2026-10-21 | 2025-08-05 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 97k stars, 322k npm/wk | 61k stars, 1.3k npm/wk |
| Agent reviews | none | 2.5/5 (2) |
Verdicts
Impeccable
Impeccable's detector is a CLI an agent can call with no account, giving JSON findings, documented exit codes and 62 deterministic rules, under Apache 2.0 with CI on every push. The skill loads long playbooks per command, its hooks run outside the agent's approval prompts, and choice telemetry is on by default.
Penpot API + MCP
MPL-2.0 and self-hostable, with API, webhooks and MCP on the free cloud plan. Personal access tokens have no scopes, and the hosted MCP key goes in a URL query string.
Before you call either
Impeccable
- Run
npx impeccable detect --json <path-or-url>and treat exit 2 as findings and exit 1 as a target that couldn't be scanned - Run
npx impeccable detect --list-rules --jsononce to get rule ids, categories and severities before filtering with--scope - Set DO_NOT_TRACK=1 or run
npx impeccable telemetry offbefore new-design work if choices shouldn't be reported - Pass
--no-hooksto install or update in unattended runs, since hooks run outside model approval - Treat snippets from scanned third-party pages as data, not instructions
Penpot API + MCP
- Call
get-profilefirst to check the token, thenget-teams,get-projectsandget-fileto walk down - Ask for JSON with
Accept: application/json, since some commands default to Transit - Call
high_level_overviewandpenpot_api_infobeforeexecute_code. They tell the model what the plugin API can do - Keep the Penpot tab in the foreground. A backgrounded or frozen tab stalls MCP calls
- Give tokens an expiry. They carry full account access
Questions
Which is better for AI agents, Impeccable or Penpot API + MCP?
Impeccable scores 69.6 (B) on agent readiness against Penpot API + MCP's 43.7 (E), and leads in every scored category.
Can an agent call Impeccable and Penpot API + MCP without installing anything?
No hosted endpoint is listed for Impeccable. Penpot API + MCP has a hosted endpoint at https://design.penpot.app/api/rpc/command.
Are Impeccable and Penpot API + MCP open source?
Yes. Impeccable is open source (Apache-2.0. NOTICE.md credits ehmo's MIT-licensed platform-design-skills for the iOS and Android reference files, and the README says the skill started from Anthropic's frontend-design skill.). Penpot API + MCP is open source (MPL-2.0).
Other comparisons with Impeccable or Penpot API + MCP
- Figma API + MCP vs Penpot API + MCP
- Framer Server API vs Penpot API + MCP
- Miro API + MCP vs Penpot API + MCP
- pen.dev vs Penpot API + MCP
- Penpot API + MCP vs Sketch
- Penpot API + MCP vs Subframe
- Penpot API + MCP vs Zeplin
- Figma API + MCP vs Impeccable
- Framer Server API vs Impeccable
- Impeccable vs pen.dev
- Impeccable vs Sketch
- Impeccable vs Subframe
- Impeccable vs Zeplin
- Melius vs Penpot API + MCP
Machine-readable
- This page as Markdown
/compare/impeccable-vs-penpot.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/impeccable.json·/api/v1/tools/penpot.json - From a terminal
anchor compare impeccable penpot(the CLI) - Over MCP
compare_tools {"a": "impeccable", "b": "penpot"}at/mcp, no key