quokkapix-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUOKKAPIX_APP_URL | No | The URL of the QuokkaPix app with agent parameter. | https://quokkapix.com/#agent=1 |
| QUOKKAPIX_SITE_ROOT | No | Override the local site root. | |
| QUOKKAPIX_RECIPE_BASE_URL | No | Override the public recipe source URL. | |
| QUOKKAPIX_PAYMENT_BASE_URL | No | Override the payment base URL. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_recipesA | List 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. |
| get_recipeA | Return 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. |
| validate_recipeA | Validate 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. |
| list_rule_profilesA | List 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. |
| get_rule_profileA | Return 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. |
| validate_result_manifestA | Validate 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. |
| process_imagesA | Process local image files through the QuokkaPix browser app using an official recipeId or a full custom recipe. Source files stay local. Without unlockToken, the browser returns an exact quote after ZIP expansion/PDF inspection and before paid processing. Retry the unchanged call with the quoted product token. |
| process_with_settingsA | Process 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. |
| list_video_recipesA | List official browser-local recipes for cutting, crop/resize, conversion, compression, audio, transcription and subtitles. |
| get_video_recipeB | Return one official Video recipe, its browser settings and expected-result QA. |
| validate_video_recipeA | Validate a custom Video recipe without opening a browser or processing media. |
| list_video_rule_profilesA | List official-source profiles for YouTube, TikTok Ads and Meta Reels video workflows. |
| get_video_rule_profileA | Return one Video profile with separate requirements, recommendations and source URL. |
| validate_video_result_manifestC | Validate quokkapix-video-result.json against its browser QA and an optional Video recipe. |
| process_videoA | Open Video in local Chromium and keep media local. Without unlockToken, return an exact duration/transcription quote before paid work; retry the same call with the product-specific token. |
| process_video_with_settingsA | Run one local video through window.QuokkaPixVideoAgent.applySettings-compatible settings, save the media or transcript output and write quokkapix-video-result.json. |
| get_payment_optionsA | Fetch live QuokkaPix Image and Video payment tiers, free limits and product-specific x402 endpoints. This tool does not sign, submit or consume a payment. |
| explain_payment_flowA | Explain the unified Image/PDF/Video x402 workflow: inspect locally, quote exactly, pay the product endpoint, optionally verify, then retry unchanged with unlockToken. This adapter can use a token but cannot sign x402 payments itself. |
| verify_unlock_tokenA | Safely preflight a QuokkaPix paid agent unlock token without consuming it. The browser consumes the one-time unlock only when the paid batch actually starts. If scope, price or currency are omitted, the tool reads live payment options first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Tools are mostly separated by media type (image/video) and action (process/list/get/validate), with detailed descriptions keeping recipe-based processing distinct from raw-settings processing. The only mild ambiguity is between process_images and process_with_settings, but their input models and workflows are explained clearly enough.
Tool names consistently follow a snake_case verb-first pattern with parallel list/get/validate prefixes across image and video domains. Minor asymmetries such as process_images vs the generic process_with_settings, and singular/plural noun mismatches, keep this from being perfectly consistent.
With 19 tools, the set is on the heavy side, largely due to mirroring nearly every image tool with a video counterpart plus payment support. Each tool does have a distinct purpose, but the total count exceeds the typical well-scoped range and may feel dense for agents.
The tool surface covers processing, official and custom recipe validation, payment quoting and verification, marketplace rule profiles, and result manifest QA for both images and video. Workflows can be completed end-to-end without obvious dead ends or missing lifecycle steps.