genMC – AI Minecraft studio
Minecraft builds and skins made by your AI agent, live in your browser tab. Export .schem.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"genmc": {
"url": "https://genmc.app/api/mcp"
}
}
}Remote endpoints
https://genmc.app/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (4)
⚪genmc_pair(code, resumeKey)
Connect to the user's open genMC studio tab. The user sees a code like "K7Q-4MX" after choosing "Connect agent" in the studio header. Pairing returns a resumeKey: if your MCP connection drops or restarts (an unknown session, a failed server), call genmc_pair with that resumeKey instead of asking the user for a new code. Resuming from another MCP session (a second client, a script) attaches it in addition: all your sessions reach the same tab. After pairing, the tab's WebMCP tools (skins, builds, whichever studio is open) appear in your tool list; if your client does not refresh it, use genmc_status and genmc_call.
Input Schema
{
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "Pairing code shown in the studio, e.g. K7Q-4MX."
},
"resumeKey": {
"type": "string",
"description": "Key from an earlier genmc_pair result; reconnects to the same tab without a new code."
}
}
}🟢genmc_status(includeSchemas)
Show whether you are paired with a genMC studio tab, whether it is reachable, which studio page it shows and which tools it offers.
Input Schema
{
"type": "object",
"properties": {
"includeSchemas": {
"type": "boolean",
"description": "Also return every tool description and input schema."
}
}
}🔴genmc_call(name, input)
Call any tool of the paired studio tab by name. Use it when your tool list has not refreshed after pairing or after the user switched studios; otherwise call the tool directly.
Input Schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Tool name, see genmc_status."
},
"input": {
"type": "object",
"description": "Tool arguments."
}
},
"required": [
"name"
]
}🟢genmc_docs(query, article, lang, limit)
Search and read the genMC knowledge base: how every studio, tool, button, limit and workflow works (skins, builds, agents and pairing, accounts and sharing, export, shortcuts, troubleshooting). Call it without arguments for the table of contents, with query to search (best matching articles with a snippet and the matching section), or with article (a slug from the contents or a search result) to read one article in full as Markdown. Links written as doc:<slug> point to other articles. Use it when you are unsure how a feature works, what a label in the studio means, or how to explain something to the user. Read-only; it never changes the studio.
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"minLength": 1,
"maxLength": 200,
"description": "Words to search for, e.g. \"secret link\" or \"export schematic\"."
},
"article": {
"type": "string",
"pattern": "^[a-z0-9-]{1,80}$",
"description": "Slug of the article to read in full, e.g. \"connect-agent\"."
},
"lang": {
"type": "string",
"enum": [
"en",
"de"
],
"description": "Language of the articles: en (default) or de."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 20,
"description": "Maximum number of search results (default 8)."
}
},
"additionalProperties": false
}Community
Evidence