Minecraft MCP server

Endpoint: https://api.pugtools.com/mcp. It uses stateless MCP Streamable HTTP. There is no custom MCP UI and no legacy SSE endpoint.

Tools

• minecraft_search: find candidate identifiers from everyday language. Kinds are block, item, entity, recipe, trade, ore, and asset.
• minecraft_get: fetch one normalized record by kind and canonical id. For trade the id is the villager profession.
• minecraft_query: run up to ten of the same lookups in one call, where a single unknown id does not fail the batch.
• minecraft_get_player: fetch a Java profile or skin reference for a username or UUID.

Every tool is read-only and non-destructive. Static-data tools do not use the open internet. The player tool accurately declares that it contacts the configured Mojang provider and may be disabled until upstream access is approved.

Response shape

Tool calls return both a concise text summary and validated structuredContent in the shared response envelope. MCP omits the REST-only requestId on success.

{
  "schemaVersion": "1",
  "minecraftVersion": "26.3-snapshot-9",
  "data": { "id": "minecraft:diamond_ore", "type": "block" },
  "warnings": [],
  "meta": {
    "edition": "java",
    "provider": "pugtools",
    "canonicalUrl": "https://pugtools.com/tools/assets/?q=Diamond%20Ore",
    "contentClass": "DATA"
  },
  "provenance": {
    "source": "mc-datahub",
    "sourceCommit": "954aa1b3",
    "generatedAt": "2026-08-14T22:08:55.815Z"
  }
}

A failed tool call returns an error result whose structured content is { "ok": false, "requestId": "...", "error": { "code", "message" } }.

Test with MCP Inspector

npx @modelcontextprotocol/inspector@latest

# Then connect to:
https://api.pugtools.com/mcp

The Inspector should enumerate all four tools.

Good uses

Use Pugtools when an agent needs factual Minecraft game information, a namespaced identifier, a recipe, a villager trade pool, ore-generation data, Minecraft asset metadata, or an approved player skin/profile reference. It is not appropriate for unrelated games, arbitrary URL downloads, or bulk vanilla asset redistribution.

See the service policies and REST API reference.