Why it exists

In Bedrock, a field name recalled slightly wrong produces output that silently does not work. No error message, no red line. Everything looks fine until the pack is loaded into the game.

A real example — both lines pass the schema, one of them never loads:

  "modules": [
-   { "type": "javascript", "entry": "scripts/main.js" }
+   { "type": "script", "language": "javascript", "entry": "scripts/main.js" }
  ]

With the top line the pack did not appear in the behavior pack list at all. It did not even raise an error. The javascript type is left over from before 1.16 and the schemas keep it for backward compatibility, but it does not load with @minecraft/server 2.x. The schema says "valid type", the game says "I cannot load this type".

That one line was measured in the real game (30-08-2026). There are seven more classes like it, all in docs/VALIDATION-LIMITS.md with ContentLog evidence.

CodeCraft closes that gap: values are read from version-pinned data, and output is validated against the official schema and against a real tsc.

Nine tools

All nine are read-only. The server writes nothing, sends data nowhere, and keeps no user data.

The order is not alphabetical, it is the order of use — and tools/list preserves it.

Setup

In Claude, open Customize → Connectors (not Settings; older guides point there, and there is no custom connector field on that screen):

1. Customize → Connectors → add a custom connector
2. Paste the endpoint address
3. Save

Three things you should see once it connects — a single "it worked" is not enough:

• The tool count is 9, complete
• The client classifies them as "read only tools" — a separate permission class
• Our own titles are visib

... View full README on GitHub