Minecraft lookups, straight from Claude
An MCP server for this API: ask Claude, ChatGPT or any MCP client for UUIDs, names and skins, and it answers with real lookups - in bulk, with your own API key, no glue code.
Connector URL
https://mcp.mc-api.ioStreamable HTTP, no session state. Authenticate with your own API key - setup per client below.
What an MCP server is
The Model Context Protocol is how AI assistants call real services: instead of pasting REST snippets into a prompt, the assistant connects to an MCP server and sees typed tools it can call on its own. This one exposes the player lookups of mc-api.io - and nothing else - so an assistant can resolve whole player lists mid-conversation.
It speaks the protocol's Streamable HTTP transport at https://mcp.mc-api.io and keeps no session state, so it behaves the same from a chat app, an agent framework or a CI job.
The three tools
lookup_uuids
Up to 50 names to UUIDs per call, Java and Bedrock. Answered per name, so one unknown player never fails the batch.
lookup_names
Up to 50 UUIDs - dashed or plain - or Bedrock XUIDs back to their current names, with the XUID alongside.
player_card
One player as a card: canonical name, UUID and the rendered skin, embedded straight into the conversation.
Bulk calls fan out onto the same cached endpoints the REST API serves, so repeated lookups stay cheap and answers carry the same data.
Connect your client
Grab a free API key from the dashboard, then add the connector. Where the setup has header fields, send the key as a header; where it only takes a URL, append it as ?key=YOUR_API_KEY.
claude mcp add --transport http mc-api https://mcp.mc-api.io \ --header "X-API-Key: YOUR_API_KEY"1. Settings -> Connectors -> Add custom connector2. Name: mc-api.io3. URL: https://mcp.mc-api.io?key=YOUR_API_KEY1. Settings -> Apps & Connectors -> Advanced settings -> Developer mode2. Create connector3. MCP server URL: https://mcp.mc-api.io?key=YOUR_API_KEY4. Authentication: None (the key rides on the URL){ "mcpServers": { "mc-api": { "type": "http", "url": "https://mcp.mc-api.io", "headers": { "X-API-Key": "YOUR_API_KEY" } } }}Once connected, just ask: "Look up the UUIDs of these 40 players" or "Show me Notch's player card".
Your key, your dashboard
The MCP server holds no API key of its own. Your client brings your key with every call, and the server passes it through to the API unchanged - so the usage shows up in your dashboard's request log, tagged with the minecraft-api-mcp user agent, right next to your other traffic.
Tool listing and discovery work without a key, so a freshly added connector is browsable before it is configured. The lookups themselves refuse to run without one and answer with setup instructions instead.
Frequently asked questions
Still stuck? The endpoint reference documents every parameter and status code.
Do I need an API key?
Yes - your own, free one from the dashboard. The MCP server holds no key itself: whatever key your client sends is passed through to the API, so every lookup shows up in your dashboard, not someone else's.
Where do I put the key?
Wherever your client lets you: an 'Authorization: Bearer' or 'X-API-Key' header where the setup has header fields (Claude Code, JSON configs), or appended to the connector URL as ?key=... where it only has a URL field (claude.ai, ChatGPT). Headers are preferred - URLs tend to end up in logs.
How many players fit into one call?
Up to 50 names or ids per lookup call. Each input is answered on its own, so one unknown name never fails the batch, and repeated inputs are folded onto a single lookup.
Which clients does it work with?
Any MCP client that speaks Streamable HTTP: Claude (claude.ai custom connectors, Claude Desktop, Claude Code), ChatGPT connectors in developer mode, and every library or agent framework with an MCP client built in.
Does it cost anything?
No. The MCP server fronts the same free API this whole site documents - the key only attributes your usage so you can see it in your dashboard.