The model thinks; a kit lets it see, edit, run, check, and undo a real file.

A kit is an MCP server that follows KHP’s tool conventions, so any MCP-capable agent can use any kit.

Scene 0.1.0: the reference implementation’s 3D scene kit, made by the protocol’s maintainer. Declares the basic tier.

Scene · Still life.kscene
Example

Call log

  1. scene_inspect (Still life.kscene, preview: true, target: {"view":"camera"}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080
  2. scene_commands (Still life.kscene, query: "material keyframe parent") ok No command has every word of `material keyframe parent`; 30 have some of them; showing the best 12.
  3. scene_run (Still life.kscene, [material.set, add.icoSphere, material.assign, add.empty, object.parent, anim.insertKey, object.transform, anim.insertKey, anim.setInterpolation]) ok Ran 9 commands on `Still life.kscene` (saved): 1920 × 1080
  4. scene_check (Still life.kscene) ok Checked `Still life.kscene`: no errors, no warnings, 1 note.
  5. scene_inspect (Still life.kscene, preview: true, target: {"view":"camera"}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080
  6. scene_inspect (Still life.kscene, preview: true, target: {"range":[0,3.75],"frames":6}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080

Preview

01 Open the scene: its objects, materials, lights and camera as JSON, and the view through the camera as the kit renders it.

The scene through its camera, as the kit rendered it: a teal ball, a sand-coloured block and a ring on a light floor.

02 Search the command catalogue for materials, parenting and keyframes.

scene_commands(Still life.kscene, query: "material keyframe parent") · 5 found

  • object.parent Parent Parents `objects` (names or ids; the selection without it) to `parent`, keeping their world transform.
  • object.clearParent Clear Parent Clears the parent of `objects` (names or ids; the selection without it), keeping their world transform.
  • object.parentArmature Parent to Armature Parents `objects` (names or ids; the selection without it) to `armature` with automatic, envelope or empty weights.
  • material.new New Material Creates a material with base color, metallic and roughness and answers its id.
  • material.set Change Material Changes material `material` (name or id): base color, metallic, roughness, emission, alpha, transmission and more.

03 The request: make the ball glossy coral, add a small faceted pebble, and put the objects on a turntable that turns once in four seconds. This kit keeps no drafts, so the edit goes to the file, saved once.

The scene through its camera, as the kit rendered it: a teal ball, a sand-coloured block and a ring on a light floor.

scene_run → 9 steps · saved

✓ material.set ✓ add.icoSphere ✓ material.assign ✓ add.empty ✓ object.parent ✓ anim.insertKey ✓ object.transform ✓ anim.insertKey ✓ undefined

changes: 2 created, 5 changed

04 Check the scene.

The scene through its camera, as the kit rendered it: a teal ball, a sand-coloured block and a ring on a light floor.

scene_check → 1 note

scene.unusedMaterial: Material Material is not used by any object → fix: material.delete

05 Look through the camera again. The clip is 48 previews of the turn, every other frame, each rendered by the kit.

06 Look at the motion: six frames from the four-second turn, in one picture the kit draws.

Six frames of the turntable’s turn, labelled with their times, as one sheet the kit rendered.

Recorded 2026-11-18 · KitionAI/kition-scene@afa92f1 Every call was made by a fixed script (scripts/record-kits.py), not chosen by a model. Kit Scene 0.1.0, served over MCP by kition 0.3.0 (the Kition SDK’s command line).The kit was built from its public repository at that commit.The pictures are the previews the kit rendered during the session.The clip is 48 previews the kit rendered through the scene’s camera, every other frame of the turn, put together with ffmpeg.

01 · The gap

Agents have a harness for code. Files have none.

A coding agent does real work because its harness lets the model read code, edit it, run it, test it, and roll back what went wrong. Slides, spreadsheets, documents, PDFs, images, video projects, and drawings have no such environment. A kit is the harness for one kind of file.

01 Observe

Code Read the source

File today A format made for storage

Through a kit

The document as JSON, typed objects, rendered previews

_inspect_query_hit

02 Act

Code Edit, run a shell

File today Scripts that guess at the format

Through a kit

Commands with parameter schemas; batches of object edits

_commands_run_batch

03 Execute

Code Compiler, runtime

File today Computing and layout locked in desktop apps

Through a kit

The kit’s own engine recalculates, lays out, and renders

engine

04 Verify

Code Tests, type checks

File today Nothing says whether the edit was right

Through a kit

Diagnostics the kit reports about the document

_check

05 Recover

Code Branches, revert

File today The edit lands in the file

Through a kit

Drafts a person reviews and merges

_draft_readyperson merges

KHP says only how an AI agent uses a kit. How a kit is built inside (its engine, data model, editor, or storage) is its own business. Why KHP →

02 · Evidence

What the pilots measured

khp-bench gives an agent the same file tasks through a KHP kit, through a flat MCP server with one tool per command over the same engine, and through plain Python scripts, and grades the files it leaves behind.

fewer tool-definition tokens than a flat MCP server, for one slide kit

With tool search off. With Claude Code’s tool search on, the gap is smaller.

Benchmark · tool definitions

fewer for three kits behind one KHP tool set, against 1,023 flat tools

The gap grows with the number of kits.

Benchmark · tool definitions

clean edits when a conversation comes back to an earlier slide

Flat MCP: 18/30 (p = 0.0001). The cause is addressing: a flat server that names the slide did as well.

Benchmark · coming back to an earlier slide

layout tasks passed under both renderers, with previews

The same kit without images: 42/50.

Benchmark · layout
Measured

These are pilot results, not a finished benchmark: few tasks, mostly one model in one agent harness. On small edits to one file the tool layer did not change success. The benchmark is run by the protocol’s maintainer, who also makes the reference implementation. Read the limits →

03 · The protocol

What KHP defines

Three roles. The kit is an MCP server for one kind of file, started on a workspace folder, with a manifest. The agent harness runs a model, its tools, and its loop, and connects to kits over MCP. The person starts the agent, reviews its drafts, and merges or discards them.

One call through KHP MCP review · merge or discard (person only) Person reviews · merges Agent harness model + tools + loop Kit MCP server · engine draft plan.gantt
  1. 01 request The person asks for a change to plan.gantt.
  2. 02 gantt_inspect → document JSON The agent reads the plan as JSON.
  3. 03 gantt_commands → schemas It finds the commands it needs.
  4. 04 gantt_run → ok · draft It moves three tasks, in a draft beside the file.
  5. 05 gantt_check → dependency-cycle · fix The check reports a dependency cycle, with a fix hint.
  6. 06 gantt_run → ok It runs the fix.
  7. 07 gantt_check → no errors It checks again: no errors.
  8. 08 gantt_draft_ready → ready It asks the person to review the draft.
  9. 09 review The person compares the draft with the file.
  10. 10 merge Only the person merges. The agent has no merge tool.
Illustration After the worked example in the specification (section 4): a Gantt kit with drafts.

Three tiers, each including the one before

Defined in section 10 of the tools page; Tiers and khp check explains how they are tested.

  1. Basic basic

    Inspect, commands, run, and check; a schema for every agent-facing command; structured errors; the safety rules. Wrapping an existing file library is enough.

  2. Agent-ready agent-ready

    Works with no editor open; real previews and checks with a catalogue; create and export; query and batch when the kit has an object model; no network.

  3. Agent-ready complete agent-ready-complete

    The layout answer for paginated kits; a guide for models; edits that address only what they change; runs sandboxed.

05 · Start

Start where you are

A

Connect a kit to your agent

Register a kit as an MCP server. This uses khp’s example kit, after the setup in its README.

Claude Code

claude mcp add docx -- "$KHP_PYTHON_ENV/bin/python" -B \
  "$REPO_ROOT/examples/docx-python/server.py" \
  --workspace "$WORKSPACE" --actor "Your Name"

Codex

# ~/.codex/config.toml (absolute paths)
[mcp_servers.docx]
command = "/path/to/venv/bin/python"
args = ["-B", "/path/to/khp/examples/docx-python/server.py",
        "--workspace", "/path/to/workspace", "--actor", "Your Name"]

Other MCP clients

{
  "mcpServers": {
    "docx": {
      "command": "/path/to/venv/bin/python",
      "args": ["-B", "/path/to/khp/examples/docx-python/server.py",
               "--workspace", "/path/to/workspace", "--actor", "Your Name"]
    }
  }
}
Connect an agent →

B

Build a kit

Wrap your file library, then test it with khp check. The checker is not on npm yet: build it from a khp checkout.

sh
git clone https://github.com/kitharness/khp && cd khp
pnpm --dir tools/conformance install --frozen-lockfile
pnpm --dir tools/conformance build
node tools/conformance/dist/cli.js check \
  --kit "my-kit --workspace {workspace}" \
  --package <kit-package> --level basic
Implement a kit →

C

Read the paper and the benchmark

The specification is four pages in the public repository. The paper explains the design; the benchmark gives the method, the pilot results, and their limits.

sh
git clone https://github.com/kitharness/khp
ls khp/spec
# agent.md  conformance.md  index.md  manifest.md

06 · Status

Where KHP stands

Version
KHP 1.1, edition 2026.11, draft
Status
Open-source protocol draft
Source
Developed in the public repository kitharness/khp. The spec pages here are copied from commit 70fab29 (2026-11-16).
Conformance
khp check is in the same repository. It is not published to npm yet.
Maintainer
Kition, which also makes the reference implementation. The protocol is meant to move to a neutral foundation later.