CodeCraftMCP server · validation & data lookup for Bedrock
https://codecraft-ashy-seven.vercel.app/mcp

Setup

REQUIREMENTS
  • A Claude client that can add a custom MCP connector.
  • Measured clients: the Claude desktop app (Pro account) and Claude Code's own MCP client. No other client has been tried, so this page does not claim it works everywhere.
  • A Minecraft Bedrock license is needed only to try the output in the game — not to use the tools.
STEPS
1
In Claude, open Customize > Connectors. Not Settings — that distinction got confused in real use.
2
Add a custom connector and enter the address.
3
Save. The tools are listed on the tool permissions screen.
https://codecraft-ashy-seven.vercel.app/mcp
HOW YOU KNOW IT WORKED
  • 9 tools should be listed.
  • The client should classify all of them as read-only; in the Claude desktop app they appear under “read only tools”.
  • Tool titles should be visible, for example “Can Bedrock do this” and “Schema summary for a document type”.
YOUR FIRST TRY

Type a request. The expected behaviour: the model calls the tools on its own, without you naming any of them. check_feasibility reads requests in Turkish and English alike; its answer is always in English.

“Make a guardian creature spawn on the surface at night”
“When I break a block, break its neighbours of the same kind too”
“Build a ten-by-ten glass box around me”
“Make it fish automatically without me touching the keyboard”
This one is blocked, with a reason and an alternative. It is a good first try because it shows the tool can say no.
THREE THINGS THAT ARE EXPECTED, NOT BUGS
GET /mcp returns 405
The spec allows a server that does not offer SSE to return 405.
No OAuth discovery endpoints
The endpoint is unauthenticated, deliberately.
Server version never appears in the client UI
A remote connector is proxied and the client does not surface the initialize response. Measured.
TROUBLESHOOTING
  • Tools not listed: check that the address ends in /mcp.
  • A call drops with a connection error: retry it. In real use, three calls dropped on a transient transport error and passed when the same payload was sent again. The cause was not on the server.
  • Tool permissions can be left on “ask every time”. There are no logs on the server, so the approval prompt is the only record of which tool was called with which arguments.