MCP SERVERRun repeatable image workflows — marketplace packs, WebP compression, metadata stripping, watermarks — in your own browser, driven by an agent.
LABSCO SUMMARY
Processing happens in the local browser, and bridge mode relays only tool settings, relative file names, status and result metadata — there is no image upload endpoint on the remote side at all, which is an unusual answer to "how does a cloud assistant edit files on my disk". The rule profiles are the other piece worth using deliberately: every marketplace requirement declares where it came from and how confident it is, and where the official public spec was thin — Temu, Mercado Libre, Shopee, parts of YouTube — the profile says secondary rather than inventing a number. Do the QA step as well: validate_result_manifest checks the output against the recipe's own contract instead of leaving you to eyeball dimensions and file sizes.
A local adapter that drives the QuokkaPix web editor in a Chromium browser on your own machine. The agent picks an official recipe or supplies settings, the adapter opens the browser, feeds files through its file input, downloads the output and writes a machine-readable quokkapix-result.json. Source image bytes stay in that browser runtime — during normal processing they are not uploaded to an image-processing server.
Node.js 20 or newer, npm, and Playwright Chromium via npx playwright install chromium, plus internet access to load the QuokkaPix app and its browser-side dependencies. Local use is npx quokkapix-mcp over stdio. Remote clients run the same package in bridge mode with explicit --input-root and --output-root: remote calls cannot read or write outside those roots, path traversal is rejected, and absolute local paths are never returned to the cloud client. Pairing is one-time, the device credential lives in ~/.quokkapix/bridge.json with owner-only permissions where the OS supports them, --pair approves another session and --reset revokes the old one.
One command — npx quokkapix-mcp
USE CASES
Find the recipe for that marketplace, read its exact settings and file limits, run it over the folder, and check the output against the QA contract afterwards.
Pull the rule profile with its requirements, recommendations, source URL and confidence — and see plainly which entries are secondary rather than official.
Run the metadata-cleanup workflow over a batch locally, so EXIF and GPS are removed without the originals leaving the machine.
Write the settings payload — resize, convert, watermark, rename in sequence — validate it before it touches a browser, then run it.
Read the current price and endpoints, follow the payment flow with an x402-capable wallet, and verify the unlock token before spending it on the run.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
explain_payment_flowExplain the current QuokkaPix x402 workflow for agents. Use this when a client needs step-by-step guidance for paid batches above the free limit: get payment options, have an x402-capable wallet/client call the paid unlock endpoint, pass unlockToken to process_images/process_with_settings, optionally verify the token, then process. This adapter can use a token but cannot sign x402 payments itself.
get_payment_optionsFetch live QuokkaPix agent payment options. Use this before any paid batch/scenario run to discover current price, currency, free single-image and small-batch rules, x402 endpoint URLs, verify endpoint and refund notes. This tool does not sign, submit or consume a payment.
get_recipeReturn one official QuokkaPix recipe by id. Use this before process_images when the agent needs exact applySettings, max file limits, payment expectations and expected result QA checks. This tool does not process images.
get_rule_profileReturn one sourced platform image rule profile by id, including requirements, recommendations, source URL, source type and confidence. This tool does not process files and does not invent missing marketplace rules.
list_recipesList official QuokkaPix local/browser image workflow recipes. Use this first when an agent needs a supported workflow for Shopify, Amazon, Google Merchant, WebP compression, metadata cleanup, social packs, watermarking, favicon generation or similar repeatable image tasks. Returns ids that can be passed to get_recipe or process_images.
list_rule_profilesList sourced image requirement profiles for marketplaces and social placements. Use this before marketplace QA when an agent needs facts for Amazon, Shopify, Google Merchant, Etsy, eBay, Walmart, TikTok Shop, Mercado Libre, Temu, Shopee, Instagram, YouTube, LinkedIn, X, Pinterest, Facebook or TikTok. Secondary sources are marked explicitly.
process_imagesProcess local image files through the QuokkaPix browser app using an official recipeId or a full custom recipe. The adapter opens local Chromium, applies settings, uploads files through the browser file input, starts processing, downloads the output and writes quokkapix-result.json. Source images stay in the local browser workflow and are not sent to a QuokkaPix processing API. Single-image runs and small batches up to 5 files are free; use unlockToken for larger paid batch/scenario runs.
process_with_settingsProcess local image files with a direct window.QuokkaPixAgent.applySettings payload instead of an official recipe. Use this for custom resize/crop/convert/compress/background/watermark/effects/rename/PDF/favicon/scenario workflows. For multi-step scenarios, prefer settings.steps as [{ tool, settings }]. The adapter downloads the output, writes quokkapix-result.json and returns QA results.
validate_recipeValidate a custom QuokkaPix recipe before using process_images. Use this when an agent generated its own recipe JSON and needs to confirm that id, applySettings.mode, applySettings.tool, optional structured steps and requires.maxFiles are valid. This is a preflight check only and does not open a browser or process files.
validate_result_manifestValidate an existing quokkapix-result.json manifest against an official recipe or custom QA contract. Use this after process_images/process_with_settings or when inspecting a previous run. It checks status, file counts, formats, dimensions, size limits, ZIP entry metadata and marketplace QA metadata; it does not read image pixels or upload files.
verify_unlock_tokenVerify a QuokkaPix paid agent unlock token before processing. Use consume=false for safe preflight checks. Use consume=true only immediately before a paid batch/scenario run above the free limit when you intentionally want to consume the unlock. If scope, price or currency are omitted, the tool reads live payment options first.
BEFORE YOU INSTALL
11 tools when we connected; the project documents 14. get_bridge_status, get_billing_status and set_unlock_token exist only on the hosted endpoint (https://quokkapix.com/mcp) with a paired local bridge, not on stdio. The remote verify_unlock_token is preflight-only and never consumes the token.
The documented client runs the server on your machine.
INSTALLATION
npx quokkapix-mcp{
"mcpServers": {
"quokkapix": {
"command": "npx",
"args": [
"-y",
"quokkapix-mcp"
],
"env": {
"QUOKKAPIX_APP_URL": "https://quokkapix.com/#agent=1"
}
}
}
}MCP servers
vipulawl
kshern
svgnew
prasadabhishek