CodeCraft
by codecraft-ashy-seven.vercel.app in Developer tools
Checks whether generated Minecraft Bedrock content will actually load. Nine read-only tools.
https://codecraft-ashy-seven.vercel.app/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 291 ms typical, 291 ms slowest 5%
- Last check
- 5 h ago
- Next check
- in 2 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"codecraft": {
"type": "http",
"url": "https://codecraft-ashy-seven.vercel.app/mcp"
}
}
}9 tools
- check_feasibility
Checks whether a user request can be built with a behavior pack and the @minecraft/server API. If it is blocked, returns why, the evidence behind that rule, and a workable alternative. Call this BEFORE writing any code or JSON: input simulation, file system access and network acc
- get_version_info
Returns which version number belongs where for this game version: min_engine_version (a three-part array), @minecraft/server module versions, the valid format_version values for every document type, and the list of recognised document types. format_version is an axis of its own a
- get_schema
Summarises the schema of a Bedrock document type: required fields, valid format_version values, and the name, type and description of every field on that node. It does not return the raw schema — that is far too large. When a node has many fields the summary narrows and says what
- lookup_id
Tells you whether a minecraft: identifier actually exists in this version and what kind it is (block, item, entity, biome, effect, enchantment, feature, dimension, camera preset, particle, potion). For a block it also returns the valid block states and the values they accept. An
- validate_json
Validates a behavior or resource pack JSON file against the official schema and returns the JSON pointer, the violated rule and a readable message for every error. Unexpected property names and the valid enum values are included in the message. Run every JSON file you produce thr
- validate_command
Validates a single Bedrock command line against the official command index: does the command exist, does the argument count match, are the selectors and block states valid. When no overload matches it returns the valid usages, and it tells you whether the command requires cheats.
- validate_script
Compiles a behavior pack script with the real TypeScript compiler against the actual @minecraft/server type definitions for that version. Returns diagnostics with line, column, TS error code and message, and reports which module versions it compiled against. Catch non-existent AP
- validate_python
Validates a Python automation script that runs OUTSIDE the game, on three axes: Python syntax (using the real interpreter), Minecraft commands embedded in the script (against the official command index), and the shape of the /connect WebSocket message envelope. For behavior pack
- review_pack
Validates every file of a behavior or resource pack in one call: it applies the right validator to each file (JSON schema, script compilation, command syntax) and then runs the checks a schema structurally cannot do — identifier consistency, filename rules, manifest module type,
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 5 h ago | Passed | 200 | 291 ms |