Lets an AI assistant pair with an open genMC studio browser tab to create Minecraft builds and skins and export .schem files.
What you can do
The server connects an assistant to the user's open genMC studio tab through a pairing code. genmc_pair establishes the connection and returns a resumeKey for reconnecting after a dropped session; genmc_status reports pairing state, the current studio page and available tools; genmc_call invokes any tool of the paired tab by name. genmc_docs searches and reads the genMC knowledge base covering studios, tools, skins, builds, agents, accounts, sharing, export and troubleshooting.
When to use it
Use it when the user is working in the genMC studio in a browser and wants an assistant to help build Minecraft structures or skins and export them as .schem files. It is also useful for looking up how genMC features and workflows work.
Requirements
A remote streamable HTTP endpoint at genmc.app; no local package, environment variables or headers are declared. The user must have the genMC studio open in a browser tab and choose Connect agent to get a pairing code.
Before you install
Pairing gives the assistant control over the user's studio tab and its tools, which can create or change builds and skins and export files. The pairing code and resumeKey act as access credentials; treat them as secrets and share them only with the intended assistant.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.genmc%2Fgenmc/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
ParameterscoderesumeKey
genmc_status
genMC connection status
Show whether you are paired with a genMC studio tab, whether it is reachable, which studio page it shows and which tools it offers. Call it when studio tools are missing from your tool list (the user switched studios): its answer also brings your tool list up to date.
ParametersincludeSchemas
genmc_call
Call a studio tool
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.
Parametersnamerequiredinput
genmc_docs
genMC knowledge base
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.
Parameterslanglimitqueryarticle
Version history
1
v1.0.0LatestOct 15, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.