QuokkaPix MCP Runner

Why STEADY

STEADY (74) for a genuinely useful architecture (cloud client, local execution, images never uploaded) described with falsifiable specificity about what the control plane carries, sensible scope separation and device revocation, and thorough per-client setup including a Windows fallback. Held below VITAL because it drives a browser UI rather than an API — inheriting that brittleness — and because the privacy boundary that is the whole value proposition has no third-party audit, version or adoption evidence behind it.

Public-surface checklist

• PASS Homepage loads (required)
• PASS Primary value prop (required) — 'Use QuokkaPix through local stdio or an OAuth-protected remote MCP bridge while image processing remains on your computer'
• PASS Cta present (required) — `npx quokkapix-mcp bridge` command plus GitHub, npm and Glama links
• PASS Pricing or access — npm package; no pricing surface on this page
• PASS Docs present (required) — Per-client setup for Claude Desktop, Cursor, Windows fallback and generic local clients
• PASS Claims specific — Names exactly what the control plane relays and states it carries no image bytes
• FAIL Third party validation — No audit of the privacy boundary, no adoption evidence

What we saw

1 screenshot captured by the Hlido engine during the reviewed run (run-4991e8e757847b97-quokkapix-com). Our own captures — not vendor marketing material.

×

←→

What it does well

• Cloud MCP clients can drive processing while every image operation runs on the local machine
• States precisely what the control plane relays — settings, relative file names, status, result metadata — and that it carries no image bytes and has no upload endpoint
• Scope separation: mcp:tools for read tools, bridge:execute additionally required for processing and staged unlocks
• `--reset` revokes the previous device before pairing a replacement
• Per-client setup for Claude Desktop and Cursor, plus a Windows `cmd /c` fallback when npx cannot be resolved
• Works with any local stdio MCP client, including LM Studio and Ollama wrappers
• Explicitly states what it is not — 'This is not a hosted image-processing API'

What it fails at

• Drives a browser UI through file inputs rather than an API — a front-end change can break the runner
• The privacy boundary is the product, yet has no third-party audit or attestation
• No version, changelog or adoption evidence on the captured surface
• Requires a local browser session, so it does not fit headless or server environments
• Not tested hands-on by Hlido — the 'no image bytes relayed' claim is the one that most needs independent verification

Pricing & access

• Pricing findable on the public surfacePASS npm package; no pricing surface on this page (tested 2026-08-09)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-09.

Related agents

• Magic Patterns Image & Design · 90
• Create images from text | AI Image Generator by Magic Studio Image & Design · VITAL 90
• Meshy Image & Design · 90

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 67/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Agent-facing by design: `npx quokkapix-mcp` runs as a local stdio MCP server, or `bridge` mode exposes an OAuth-protected remote endpoint at https://quokkapix.com/mcp for cloud clients. Tools such as list_recipes, process_images and process_with_settings are called directly by the agent, which must pass real local file paths.

Agent-friendly score: 8/10

Evidence

• Local stdio MCP adapter processes images in a local browser; an OAuth-protected remote bridge lets cloud clients drive it — source (2026-08-09) verified
• Control plane relays settings, relative file names, status and result metadata; no image upload endpoint; does not relay source or output image bytes — source (2026-08-09) verified
• mcp:tools scope permits read tools; processing and staged unlocks additionally require bridge:execute — source (2026-08-09) verified
• Documented Claude Desktop and Cursor config plus a Windows `cmd /c` npx fallback — source (2026-08-09) verified
• Exposes tools including list_recipes, process_images and process_with_settings — source (2026-08-09) verified
• Third-party audit of the stated privacy boundary — source (2026-08-09)
• Version, changelog or adoption evidence — source (2026-08-09)