API terms and policies

Last updated: August 16, 2026.

Use and availability

The public API and MCP server are offered as a read-only developer service without a guaranteed uptime SLA. Do not use them to violate Mojang, Microsoft, or third-party terms, bypass access controls, or create a bulk mirror of Minecraft game assets.

Rate limits

The default safety limit is 120 requests per minute per connecting IP. Limits may change to protect availability. A 429 response includes Retry-After and rate-limit headers. Clients should cache versioned data and use exponential backoff for upstream errors.

Versioning

Breaking HTTP changes use a new path version. Additive fields may appear within /v1. Every response identifies its Minecraft dataset version and schema version. Unsupported Minecraft versions fail explicitly rather than silently returning a different version.

Privacy and logs

The service logs request category, MCP tool name, success/failure, duration, result quality, requested data kind, version selection, cache status, upstream provider, error class, and normalized static resource identifiers. MCP client software may self-report an application name and version; those two fields may be retained to measure interoperability. User prompts, arbitrary request bodies, player usernames, UUIDs, skin URLs, and personal information are not intentionally logged. See the site privacy policy.

Minecraft content

The API provides normalized data, identifiers, calculations, Pugtools analysis, and metadata. It does not provide bulk/raw vanilla textures, models, sounds, archives, or a general asset filesystem. Player skins are returned as temporary upstream Mojang references rather than mirrored files.

Support

Include the X-Request-Id when reporting an API problem through the project GitHub account.

Unofficial service

NOT AN OFFICIAL MINECRAFT WEBSITE. NOT APPROVED BY OR ASSOCIATED WITH MOJANG OR MICROSOFT.