SlopCamera
Browse documentationReference · The SlopCamera MCP toolset

Reference

The SlopCamera MCP toolset

The 21 fixed tools slopcamera mcp serves over stdio, their bounds, and what stays CLI-only.

slopcamera mcp --root /absolute/workspace serves a fixed toolset over stdio: newline-delimited JSON-RPC at protocol version 2025-11-25, server name hraness-slopcamera, with protocol messages as the only stdout surface. Cursor, Claude Desktop, and other MCP-capable clients register it as a local command; every path the tools accept stays relative to the selected root.

The fixed toolset

The server exposes 21 named tools. Four general tools:

ToolEffect
check_diagramParse and lint one .diagram.json source. Read-only.
render_diagramWrite the five artifacts a CLI render produces: .tldr, light and dark SVG, and light and dark PNG.
search_slopcameraSearch the fixed operation registry by bounded text. Never executes anything.
execute_slopcameraRun one exact operation code with typed JSON input.

execute_slopcamera admits ten operation codes: slopcamera.diagram.check, slopcamera.diagram.render, slopcamera.image.vectorize, slopcamera.image.generate, slopcamera.image.icon, slopcamera.image.gallery, slopcamera.icon.compose, slopcamera.icon.render, slopcamera.soundtrack.compose, and slopcamera.soundtrack.grid. Thirteen read-mostly scene tools inspect, plan, and audit without mutating project state:

ToolsEffect
check_scene, inspect_scene, diff_scenesValidate, summarize, or compare scene JSON sources
evaluate_scene, audit_scene, audit_scene_temporalSample world state and report spatial or temporal findings
check_scene_direction, plan_scene_direction, plan_scene_galleryCheck a direction document, compile proposals, plan bounded variants
check_scene_effects, plan_scene_effectsCheck declared effects and bind them to a render plan
check_scene_behavior, audit_scene_behaviorCheck a behavior document and audit its declared behavior

Four local tools compose and render vector icon scenes and read soundtrack scores. They make no model or network request and write only optional outputs inside the root:

ToolEffect
compose_icon, render_iconSolve an icon scene, collection, construction program, or recipe; draw it to inert SVG or replay a recipe (slopcamera.icon.compose, slopcamera.icon.render)
compose_soundtrack, derive_soundtrack_gridVerify a loop, song, or MIDI file; derive its bpm, beatOffsetUs, beatsPerBar, and section cue times (slopcamera.soundtrack.compose, slopcamera.soundtrack.grid)

No surface accepts source text, evaluates caller code, executes workspace configuration, or registers a new operation. Renders run one at a time. Older releases expose a smaller toolset; restart the client and call tools/list to discover the installed server.

Bounds

  • Paths are root-relative. Absolute paths and .. segments reject, and links resolve inside the root before any read or write.
  • Diagram sources must end in .diagram.json, fit in 1 MiB, and hold at most 64 shapes and 128 edges; checks and renders return at most 40 findings.
  • render_diagram accepts an optional out_dir and a scale of at most 4; the scaled canvas may not exceed 16,777,216 pixels and overwrites the five artifacts atomically.
  • Scene, direction, and effects JSON must end in .json and fit in 1 MiB.
  • Icon sources and soundtrack scores fit in 1 MiB, and each written SVG, recipe, score, or grid fits in 4 MiB. Icon renders are 16 to 1024 pixels on an edge; a grid holds at most 512 sections and a start_us of at most one hour. Out-of-range arguments reject before a resource lease.
  • slopcamera.image.vectorize reads a raster inside the root up to 16 MiB and writes an inert SVG inside the root.
  • slopcamera.image.generate takes a provider/model id, a prompt, and a root-relative outputPath, then sends one non-retried request through the Gateway contract using the server process's environment credential. Icon and gallery codes can also make paid requests.

What stays outside

The server is deliberately a subset: it exposes no recording, project, studio, or workflow command. For the full local surface, use the CLI and Agent Skill, or see Use SlopCamera from an MCP client for setup.