MCP server for interacting with the Scryfall MTG API
CodeCraft is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Checks whether generated Minecraft Bedrock content will actually load. Nine read-only tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http codecraft-mcp https://codecraft-ashy-seven.vercel.app/mcp
# 2 — ask your agent for something these tools do
# check_feasibility, get_version_info, get_schema and 6 more
CodeCraft costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http codecraft-mcp https://codecraft-ashy-seven.vercel.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 access do not exist in the Bedrock scripting API, and those are the most commonly hallucinated APIs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request | string | yes | The user request in their own words. Any language is accepted. |
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 and is unrelated to the game version. Call this before writing any behavior pack file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
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 was shortened in the truncated field; use path to descend into a child node for full detail. Call this before writing a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Document type, e.g. "behavior/blocks", "behavior/entities", "behavior/spawn_rules". The full list is in the get_version_info output. |
| path | string | no | Path to descend into the schema, separated by "/". For example "minecraft:entity" or "minecraft:entity/components/minecraft:health". Omit it to get the root summary. An unresolvable path returns an er |
| version | string | no | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
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 identifier without a namespace is treated as minecraft:. Verify every identifier here before writing it — an identifier
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Identifier, e.g. "minecraft:blaze" or just "blaze" without the namespace. |
| version | string | no | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
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 through this before handing it to the user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | The complete file content as text. Parse errors are reported too. |
| type | string | yes | Document type. A canonical name ("behavior/blocks/blocks"), a short form ("behavior/blocks") or a file path ("BP/blocks/ruby.json") are all accepted. The list of recognised types is in the get_version |
| version | string | no | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
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. Run every command through this before giving it to the user. execute ... run <command> chains are resolved: the comma
| Parameter | Type | Required | Notes |
|---|---|---|---|
| line | string | yes | A single command line, e.g. "/give @p diamond 1". The leading / is optional. |
| version | string | no | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
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 APIs and calls removed in later versions here — Bedrock scripting APIs written from memory are the most common source of o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The complete script content. JavaScript or TypeScript. |
| version | string | no | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
| channel | string | no | Module channel. Defaults to stable. If beta is requested but a module has no beta release it falls back to stable — the modules field in the result says which version each module was compiled against. |
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 scripts use validate_script instead — Python does not run inside a pack. The embedded command check is the most valuable
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The complete Python script content. |
| version | string | no | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
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, texture keys, component names, Molang queries and loot/trade table paths. This is the LAST step before handing a pack to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| files | array | yes | The files in the pack. Include the manifest — several checks depend on it. |
| version | string | no | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CodeCraft or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish CodeCraft can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.