What the paprika3d plugin adds

The stable build lists 16 tools, nine skills, two Claude Code hooks, and a few files in your project. This page lists them all; the tools page has each tool's full description, as the server registers it, and How it works shows how paprika-make and paprika-loop use them.

The 16 tools, by stage

In Claude Code a tool's full name is mcp__plugin_paprika3d_paprika__<tool>; from a project's .mcp.json it is mcp__paprika__<tool>. They are grouped here in the order of the flow How it works describes; every MCP client gets all 16.

References and design spec

Used by paprika-make for the references and the sheets; reference also checks a page against a picture.

Tool Reach for it when What it does
reference The page should match a picture Reads the picture with no page open (a crop with a pixel grid, colours at points); compare puts the page beside it, with the differences by region
sheet A brief needs a look board or character sheets, or you want to know which image and 3D keys are set check: true names the keys found (never a value), recommends a provider with its listed price, and lists running jobs. pictures (each with an optional crop and label), palette and notes with no provider compose a free sheet in Chrome, refs/sheets/LOOK.png or out; nothing is sent anywhere. With provider and prompt, kind: "board" draws a look board and "turnaround" a character's front, side and back views (fal, OpenAI, Gemini), and "model" starts a 3D model job from a picture (fal, Meshy, Tripo), each billed to your key. remember: "yes" keeps a yes to picture sheets across projects; "ask" forgets it (preview)

Build

Models for the page: found, built in code, seen and checked.

Tool Reach for it when What it does
asset_search The page needs a ready-made model, PBR texture or HDRI sky Finds one by words or by a crop of a picture, with a contact sheet; save writes that sheet to a file under the project (refs/assets/fox.jpg), as the picking round does. pick downloads one into the project with its loading code and its credit line. Model searches are logged to paprika3d/sourcing.json (preview)
model_run A model is faster to build in code than to find Builds it in a modelling scene kept between calls (three.js and Manifold: booleans, hull, extrude, revolve) and saves a .glb the page loads; load also reads .obj and .fbx, so a web download becomes a GLB. searched logs why a thing is built in code ("by design: terrain") to paprika3d/sourcing.json, which the critic and a loop's judge read. The first run that adds geometry in a project with no model search on record says so in one line (preview)
model_look You need to see that model true to size Shows the modelling scene from the front, right, top and three-quarter against a grid, with each object's size, triangles, closed or open edges, volume and genus (preview)
model_audit The page loads .glb, .gltf or USD files Checks each file's size, triangles, textures and compression, with a site or Shopify verdict; shrink rewrites a .glb or .gltf smaller

See

Tool Reach for it when What it does
open A three.js, R3F or WebGL page has been written or changed Runs the page (a file or folder, an http URL or a dev-server command) in headless Chrome on a paused, seeded clock, and reports the files that loaded and failed, dev-server errors, an unsized canvas and old or removed three.js APIs. Up to 4 pages at once; browser: "firefox" uses the installed Firefox (preview)
look You need to see what a viewer sees Shows a screenshot and names every object on screen and every one never seen, with its size and where it is, plus the lighting, z-fighting, canvas and HTML-overlay faults. Modes: target, cameras, sheet, viewports, scroll, zoom, sample, at, opening, save, compare
observe You need the state without acting Reads the state as JSON (window.__game.observe(), or the named three.js objects), with renderer counts, new console errors and what changed
eval You need a number the other tools do not give, or to try a change before writing it Runs any JavaScript in the page with scene, camera, renderer, find and stats in scope; save writes what it returns to a file

Play and test

Tool Reach for it when What it does
interact You need to play an interaction the request names Plays keys, mouse, touch, wheel, scroll, resize and clock steps on exact frames, and reports what changed in the state. { state }, until, trace and expect steps; save keeps the play as a check; record: true makes a real-time GIF
feel You need to know whether a hit, pickup or win lands on screen Measures camera shake, scale pops, eased moves versus teleports, flashes, particles, spawns, HUD ticks and sounds after the steps
test After an edit that could break an earlier feature Reruns every saved check from a fresh reload, one pass or fail line each

Measure

Tool Reach for it when What it does
perf A reply says the frame is over budget, or the user asks about speed Times the frame: frame time, draw calls, triangles and asset size against a budget; variants in one call, costs by named group, throttle, network. With optimize: true it speeds the page up instead: tries the runtime's switches (resolution, defaults, instancing, LOD, dispose) one at a time, keeps in game-runtime.json only the ones that help without changing the picture, and ends with the final test when the project has saved checks

Share

Tool Reach for it when What it does
publish Only when the user asks for a public link Puts the built page on https://<name>.paprika3d.app (preview, invite-only)
send_feedback A paprika3d reply was wrong, unclear or got in the way Sends the paprika3d team a bug or criticism, with the last tool call's name, options and error

The skills

Skill What it does
threejs-game Loads by itself for any three.js page: build the first version whole and as impressive as it can be, then what each tool shows; the window.__game convention, and references for lighting, geometry, effects, performance and model files
/paprika3d:paprika-make <request> Asks a few questions, one at a time after a first batch (what it is, a web search for study references, picture sheets, the kind of models), gathers the pictures to work from (when you have none, a subagent finds some and you confirm them), writes a style sheet (LOOK.md), character sheets (CHARACTERS.md) and for a game a design doc (DESIGN.md, yours read and added to, never overwritten), asks where each key asset comes from (the library, a free model on the web, generated with your key, or code), writes a short brief to BRIEF.md, and builds the page in this session. Study references stay in refs/study/ and are never published
/paprika3d:paprika-loop <request> for <time> Starts only when you type it. Builds from the same brief, unattended until the time is up: fresh claude -p sessions, a builder then a read-only judge each round, a commit per round and the best tagged paprika-loop/best. Edit paprika-loop/PROMPT.md while it runs to change the request. Each round is two Claude Code sessions, billed as such; needs claude and git on PATH
paprika-publish Tells the agent when to publish and what to tell you
threejs-screenshot, threejs-play, threejs-test, threejs-perf, threejs-glb-audit One task each, for an agent that searches for it: which tool sees the scene (open, look), plays it (interact), keeps and reruns checks (interact save, test), times the frame (perf) or checks model files (model_audit), with threejs-game for the method

The slash commands, automatic skill loading and the hooks are Claude Code features; other agents get the same method from AGENTS.md and skills/threejs-game/SKILL.md.

The hooks (Claude Code)

Hook What it does for you
After each batch of edits Reruns the checks saved with interact's save and rechecks the page's Lighting: and Surfaces: lines on the reloaded page; it speaks only when one starts or stops failing. Once per session it says a three.js page the agent wrote has not been opened
On the first stop States once the edits never played or looked at and the faults still open

The files it puts in your project

File Written by What it is
geo.js open Procedural geometry with Manifold built in: booleans, hull, extrude, revolve, seeded scatter
fx.js open Sound effects made in code, canvas textures, particle bursts, a first-load stage (tone mapping, environment, shadowed light, resize), metre-scale texture coordinates, placement rules, a reference picture's camera
game-state.js, physics-worker.js the agent, as the skill says Game state in typed arrays with a generated window.__game, rewind, and Rapier physics in a worker
three-runtime.js perf with optimize: true The switches it keeps, read from game-runtime.json

geo.js and fx.js are written on the first open and replaced only when the plugin's copy changes; leave them in place.

Where runs go

paprika3d/runs/<time>/: one folder per open. Each open deletes the pictures and clips (.png, .gif, .mp4) of all but the newest 10 run folders, keeping run.json, last-test.json and every other file; a folder written to in the last hour is left whole. Saved baselines live in paprika3d/baselines/. Add paprika3d/ to the project's .gitignore.

The asset library

asset_search reaches a hosted library at assets.keeno.dev, with over 62,000 assets:

Kind Count Licence Source
Models 57,732 CC BY 4.0 or CC0 Objaverse, web-ready; 549 AI-generated, from Scenario's 3D Collection
PBR textures 3,545 CC0
HDRI skies 1,430 CC0

Updated 2026-10-30.