Quokkapix MCP Server

Local-first MCP adapter and cloud-to-local execution bridge for QuokkaPix image workflows. The quokkapix mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

• prepare product photos for Shopify, Amazon, or Google Merchant;
• validate marketplace and social image outputs against sourced rule profiles;
• compress images to WebP for a website;
• remove EXIF/GPS metadata;
• generate social media image packs;
• watermark a batch of images;

Its toolset

Everything the assistant can do here goes through one of these:

• list_recipes — Use first when the agent does not know which workflow to run
• get_recipe — The get_recipe tool exposed by this server
• validate_recipe — The validate_recipe tool exposed by this server
• list_rule_profiles — Use this when an agent needs facts for Amazon, Shopify, Google Merchant, Etsy, eBay, Walmart, TikTok Shop, Mercado Libre, Temu, Shopee, Instagram
• get_rule_profile — Agents can pass the returned facts into their own planning, or call validate_result_manifest with ruleProfileId
• validate_result_manifest — This is useful when an agent wants to inspect a previous run and decide whether the output is acceptable
• process_images — It opens a browser, applies the recipe, uploads files, starts processing, downloads the output, writes quokkapix-result.json, and returns QA results
• process_with_settings — Processes local image files using a direct QuokkaPix applySettings payload
• get_payment_options — The get_payment_options tool exposed by this server
• explain_payment_flow — Important: this local MCP adapter does not sign x402 payments by itself. An x402-capable client or wallet must call the paid unlock endpoint and
• verify_unlock_token — Only use consume: true if you intentionally want to consume the unlock immediately

Configuration

You will need 4 environment variables: QUOKKAPIX_APP_URL, QUOKKAPIX_RECIPE_BASE_URL, QUOKKAPIX_PAYMENT_BASE_URL, QUOKKAPIX_ALLOW_CUSTOM_APP_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >=20 - npm - Playwright Chromium - internet access for loading QuokkaPix and browser-side dependencies/models when needed - local file paths that the MCP process can read Bridge mode additionally requires explicit input and output roots. Remote calls cannot read or write outside those roots. Install dependencies:

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Quokkapix's toolset — list_recipes, get_recipe, validate_recipe and 8 more — is a fair guide to whether it matches your workflow. It is maintained by quokkapix; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Quokkapix's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Quokkapix.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the quokkapix mcp server does with a few real requests.