Koskamo

CodeCraft MCP

CodeCraft is a stateless, read-only MCP server for Minecraft Bedrock that validates generated content against official schemas and game logic. It provides nine tools to check feasibility, version info, schema compliance, identifier existence, JSON validity, command syntax, script compilation, and full pack reviews, helping developers catch silent failures before loading packs in-game.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

CodeCraft MCP logo, by TanerTalasCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by TanerTalas
MCP endpoint (Streamable HTTP)
https://codecraft-ashy-seven.vercel.app/mcp
Vendor documentation

What its tools do

9 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (9)

9 of 9 have a description · 9 of 9 declare behavior hints · 9 of 9 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Validate if a generated Bedrock feature or entity will load without errors
  • Check if a specific minecraft: identifier exists and retrieve its block states
  • Verify JSON files match the official schema for a given format version
  • Review an entire Bedrock pack for structural and logical consistency

Source and maintenance

Community listingRegistry 0.1.0
mcp-registry: io.github.TanerTalas/codecraft@0.1.0Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
codecraft 0.1.0
MCP protocol negotiated in check
2025-11-25
Tools
9 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Tools for producing verified Minecraft Bedrock content. Order matters: call check_feasibility first (can Bedrock do this at all), then get_version_info and get_schema (which fields are required, what format_version to use), and review_pack after you have written the files. Bedrock's version fields are easy to confuse — format_version is NOT the game version, it is the schema version of that specific file type. Read these values from the tools, not from memory.

Tools

9 advertised

check_feasibility — Can Bedrock do this
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

check_feasibility input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "request"
  ],
  "properties": {
    "request": {
      "type": "string",
      "minLength": 1,
      "description": "The user request in their own words. Any language is accepted."
    }
  }
}
check_feasibility annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_version_info — Bedrock version and schema context
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_version_info input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "version": {
      "type": "string",
      "description": "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."
    }
  }
}
get_version_info annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_schema — Schema summary for a document type
Advertised by the server during the last successful anonymous check.
Advertised read-only

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 file to learn which fields are required and what format_version must be.

get_schema input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "type"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "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 error that lists the valid fields on that node."
    },
    "type": {
      "type": "string",
      "minLength": 1,
      "description": "Document type, e.g. \"behavior/blocks\", \"behavior/entities\", \"behavior/spawn_rules\". The full list is in the get_version_info output."
    },
    "version": {
      "type": "string",
      "description": "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."
    }
  }
}
get_schema annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
lookup_id — Verify a vanilla identifier
Advertised by the server during the last successful anonymous check.
Advertised read-only

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 that does not exist fails silently in the game.

lookup_id input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Identifier, e.g. \"minecraft:blaze\" or just \"blaze\" without the namespace."
    },
    "version": {
      "type": "string",
      "description": "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."
    }
  }
}
lookup_id annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
validate_json — Validate Bedrock JSON against its schema
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

validate_json input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "content",
    "type"
  ],
  "properties": {
    "type": {
      "type": "string",
      "minLength": 1,
      "description": "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_info output."
    },
    "content": {
      "type": "string",
      "minLength": 1,
      "description": "The complete file content as text. Parse errors are reported too."
    },
    "version": {
      "type": "string",
      "description": "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."
    }
  }
}
validate_json annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
validate_command — Validate a Bedrock command
Advertised by the server during the last successful anonymous check.
Advertised read-only

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 command after run is validated too, including nested execute.

validate_command input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "line"
  ],
  "properties": {
    "line": {
      "type": "string",
      "minLength": 1,
      "description": "A single command line, e.g. \"/give @p diamond 1\". The leading / is optional."
    },
    "version": {
      "type": "string",
      "description": "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."
    }
  }
}
validate_command annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
validate_script — Compile an @minecraft/server script
Advertised by the server during the last successful anonymous check.
Advertised read-only

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 output that fails silently.

validate_script input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "minLength": 1,
      "description": "The complete script content. JavaScript or TypeScript."
    },
    "channel": {
      "enum": [
        "stable",
        "beta"
      ],
      "type": "string",
      "description": "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."
    },
    "version": {
      "type": "string",
      "description": "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."
    }
  }
}
validate_script annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
validate_python — Validate an automation script
Advertised by the server during the last successful anonymous check.
Advertised read-only

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 one: a command written from memory can look syntactically fine and still do nothing in the game. Only strings starting with / are treated as commands. If syntax could not be checked, syntaxChecked is false in the result; ok:true alone does not mean the syntax is valid.

validate_python input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "minLength": 1,
      "description": "The complete Python script content."
    },
    "version": {
      "type": "string",
      "description": "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."
    }
  }
}
validate_python annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
review_pack — Validate a whole pack
Advertised by the server during the last successful anonymous check.
Advertised read-only

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 the user, and it is both faster and broader than validating each file separately.

review_pack input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "files"
  ],
  "properties": {
    "files": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path",
          "content"
        ],
        "properties": {
          "path": {
            "type": "string",
            "minLength": 1,
            "description": "Path inside the pack, e.g. \"behavior_packs/ruby/blocks/ruby_ore.json\"."
          },
          "content": {
            "type": "string",
            "description": "The complete file content."
          }
        }
      },
      "minItems": 1,
      "description": "The files in the pack. Include the manifest — several checks depend on it."
    },
    "version": {
      "type": "string",
      "description": "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."
    }
  }
}
review_pack annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
579 ms
95th percentile latency
579 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 579 ms · metadata changed · 9 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http codecraft-mcp https://codecraft-ashy-seven.vercel.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add codecraft-mcp --url https://codecraft-ashy-seven.vercel.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable codecraft-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "codecraft-mcp": {
      "url": "https://codecraft-ashy-seven.vercel.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "codecraft-mcp": {
      "type": "streamableHttp",
      "url": "https://codecraft-ashy-seven.vercel.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start codecraft-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "codecraft-mcp": {
      "type": "http",
      "url": "https://codecraft-ashy-seven.vercel.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http codecraft-mcp https://codecraft-ashy-seven.vercel.app/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://codecraft-ashy-seven.vercel.app/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "codecraft-mcp": {
      "serverUrl": "https://codecraft-ashy-seven.vercel.app/mcp"
    }
  }
}

Let your agent find its tools

Find servers like CodeCraft MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 8,312