Log inSubmit server
Quokkapix MCP logo

Quokkapix MCP

by quokkapix

Run private image and video workflows in local Chromium through MCP, with recipes, QA manifests, marketplace profiles, and optional bridge mode.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Quokkapix MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "quokkapix-quokkapix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "quokkapix-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

The quokkapix/quokkapix-mcp MCP server connects MCP clients to local Chromium for browser-based QuokkaPix image and video processing. It uses Playwright and QuokkaPix agent APIs to process local media, save outputs, and write machine-readable result manifests without sending source media to a processing server. Use it for repeatable resize, conversion, compression, metadata, watermark, marketplace QA, video, audio, transcription, and subtitle workflows. Local stdio suits desktop clients, while bridge mode coordinates remote clients with a paired computer.

Use cases

  • Prepare product images for marketplace listings
  • Compress local images into WebP files
  • Generate favicon and social media packs
  • Process and subtitle local videos
  • Validate media outputs against sourced platform rules

Key features

  • Local Chromium image and video processing
  • Official and custom recipe workflows
  • Marketplace and social rule profiles
  • Machine-readable image and video QA manifests
  • Optional remote bridge mode
  • x402 quote and unlock-token support

Tools19

What Quokkapix MCP lets your agent do. Expand a tool for its parameters.

Verified live~8.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · quokkapix-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads143Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Tools exposed19Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Quokkapix MCP works

What quokkapix/quokkapix-mcp MCP server does

The quokkapix/quokkapix-mcp MCP server provides an MCP interface for local QuokkaPix Image and Video browser workflows. It opens the relevant QuokkaPix surface in local Chromium, selects files through the browser input, applies an official recipe or supplied settings, downloads the result, and writes a result manifest. Image jobs produce quokkapix-result.json; video jobs produce quokkapix-video-result.json.

Supported work includes image resizing, cropping, conversion, compression, background removal, metadata stripping, watermarking, renaming, PDF and favicon workflows, and export packs. Video workflows cover cutting, cropping, resizing, conversion, compression, audio operations, local transcription, and subtitle output. The supplied tools also expose sourced image and video requirement profiles for marketplace, social, YouTube, TikTok Ads, and Meta Reels use cases.

How it works

The adapter uses Playwright to control local Chromium and calls window.QuokkaPixAgent for images or window.QuokkaPixVideoAgent for video. Processing happens in the browser runtime. The package does not provide a server-side media-processing API, and local file paths are available only to the local runner.

In stdio mode, an MCP client communicates directly with the local process. Bridge mode adds a remote control path: a remote MCP client sends commands, relative file names, status, and result metadata through the QuokkaPix control plane, while the paired bridge performs the work on the user's computer. The bridge does not relay source or output media bytes and restricts access to its configured input and output roots.

Setup and configuration

The quokkapix/quokkapix-mcp MCP server requires Node.js 20 or newer, npm, Playwright Chromium, internet access for QuokkaPix and browser-side dependencies when needed, and readable local file paths. Install dependencies with npm install and install Chromium with npx playwright install chromium. A basic launch is:

Terminal
npx quokkapix-mcp

For remote clients, start bridge mode with explicit directories:

Terminal
npx -y quokkapix-mcp bridge --input-root /absolute/path/to/input --output-root /absolute/path/to/output

Approve the printed pairing URL, add https://quokkapix.com/mcp as a remote MCP connector, and complete OAuth authorization. --pair authorizes another browser session; --reset revokes the previous device authorization and creates a new credential. Bridge credentials are stored in ~/.quokkapix/bridge.json.

Tools and capabilities

Recipe and validation tools support a staged workflow:

  • list_recipes and list_video_recipes show official image and video workflows.
  • get_recipe and get_video_recipe return settings, limits, expected results, and payment information.
  • validate_recipe and validate_video_recipe check custom definitions before processing.
  • list_rule_profiles, get_rule_profile, list_video_rule_profiles, and get_video_rule_profile expose sourced requirements and recommendations.
  • validate_result_manifest and validate_video_result_manifest inspect existing QA manifests without reading image pixels or uploading files.

process_images and process_video run official or custom workflows. They can return an exact payment quote before paid processing when no unlock token is supplied. process_with_settings and process_video_with_settings apply direct agent-compatible settings. Payment-related tools fetch options, explain the x402 sequence, and preflight an unlock token; they do not sign or submit payments.

Limitations and notes

Browser memory limits still apply. This package is not a hosted processing service, GPU or CPU backend, or a mechanism for passing local paths to QuokkaPix by URL. Internet access may be needed for browser dependencies and locally used transcription models. Local transcription can download and cache Whisper model files, but the selected media is not uploaded with that model request.

Marketplace profiles identify their source type, URL, and confidence, and may be secondary or category- or country-specific where public official specifications are limited. Manifest validation checks reported metadata and supported QA fields; it does not inspect image pixels unless pixel QA data is already present in the browser result manifest.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Quokkapix MCP

quokkapix/quokkapix-mcp is an MCP server that connects MCP clients to local Chromium and QuokkaPix Image and Video browser workflows. Its main tools list and validate recipes, process local media, apply direct settings, check marketplace rules, validate result manifests, and explain or verify payment unlocks without sending source media to a processing server.

Install Node.js 20 or newer, run `npm install`, install Chromium with `npx playwright install chromium`, then start it with `npx quokkapix-mcp`. The package also requires npm, internet access for QuokkaPix and browser dependencies when needed, and readable local file paths.

Yes, Cursor is named as a compatible local stdio MCP client. Start the package locally with `npx quokkapix-mcp` and configure Cursor to launch the command as an MCP server.

Use bridge mode with explicit input and output roots, approve the pairing URL, add `https://quokkapix.com/mcp` as a custom remote connector, and complete OAuth authorization. Remote calls use relative paths within those roots and receive commands, status, and result metadata rather than media bytes.

No, source image, video, audio, and output bytes remain on the user's computer during browser processing. Bridge mode relays settings, relative file names, status, and metadata through the control plane, but it has no media upload endpoint.

Related MCP servers

All in Art & Culture All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewQuokkapix MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/quokkapix-quokkapix-mcp?style=directory)](https://allmcps.com/mcp/quokkapix-quokkapix-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/quokkapix-quokkapix-mcp"><img src="https://allmcps.com/api/badge/quokkapix-quokkapix-mcp?style=directory" alt="Quokkapix MCP on AllMCPs" /></a>