Voxel Architect AI — MCP Server
liquidmongoose/voxel-architect
Gera conceitos visuais de arquitetura Minecraft via IA
Ver no GitHubServidor MCP que capacita assistentes de IA (Claude, Gemini, ChatGPT) a gerar imagens conceituais de construções Minecraft. Inclui interface web local em vanilla JavaScript, galeria mobile e controle remoto. Integra-se com API backend para geração de imagens com reconhecimento de screenshots.
Instalação
npx convez-ai liquidmongoose/voxel-architect1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Designers criando protótipos visuais de builds Minecraft automaticamente
- Streamers e criadores gerando conceitos arquitetônicos a partir de capturas de tela
- Arquitetos virtuais explorando estilos e temas via IA com controle remoto mobile
Veredito

Ferramenta niche mas bem-arquitetada para fãs de Minecraft que usam IA. A integração com MCP é sólida e a documentação cobre casos de uso legítimos (design, streaming). Requer chave de licença e backend externo, limitando adoção casual.
README
A tradução para o português deste README ainda está na fila.
Voxel Architect AI — MCP Server
An MCP server that gives AI assistants (Claude, Gemini, ChatGPT, etc.) the ability to generate Minecraft build concept images. Also runs a local vanilla JS web app at http://localhost:8383 for browser-based access and a mobile gallery/remote control.
This component is the MCP server + local web frontend only. All AI generation is handled by the backend API (Component B). This repo does not call Google AI APIs directly.
Requirements
- Node.js 20+
- A valid Voxel Architect AI license key
- The backend API must be reachable (local Docker, staging, or production)
Installation
npm install
Configuration
Config lives at ~/.voxel-architect/.env — outside the repo, never committed:
ARCHITECT_UNLOCK_KEY=your-license-key-here
# BACKEND_URL defaults to https://api.voxelarchitect.ai — only set this to override
# BACKEND_URL=http://localhost:8787 # local dev
# BACKEND_URL=https://staging-api.voxelarchitect.ai # staging (also requires EXTRA_API_HEADERS)
EXTRA_API_HEADERS={"CF-Access-Client-Id":"...","CF-Access-Client-Secret":"..."} # staging only
After editing this file, issue /mcp reload in your AI client.
Running locally
npm start
Web app available at http://localhost:8383. MCP server runs on stdio.
npm scripts
| Script | Description |
|---|---|
npm start | Dev mode — starts MCP server + web app |
npm run lint | ESLint across src/ |
npm run build | Bundle → dist/bundle.js (CJS, node20) via esbuild |
npm run package | lint + build + pkg → standalone binaries in dist/ |
npm run inspect | Interactive tool testing via mcp-inspector |
No test suite — the test script exits 1.
Local data
All runtime data lives at ~/.voxel-architect/:
| Path | Contents |
|---|---|
outputs/ | Generated PNGs, secured screenshots, uploads |
outputs/manifest.json | Generation history (newest first) |
theme.md | Active architectural style spec |
config.json | { autoOpenImages, enableMemory, captureScreen } |
pending_command.txt | One-shot mobile command file |
.env | ARCHITECT_UNLOCK_KEY, BACKEND_URL, EXTRA_API_HEADERS |
Minecraft screenshots are read from:
- macOS:
~/Library/Application Support/minecraft/screenshots/ - Windows:
%APPDATA%\.minecraft\screenshots\
MCP tools
| Tool | Description |
|---|---|
get_architect_status | System health: unlock status, backend connectivity, credits |
set_unlock_key | Save and verify the license key in ~/.voxel-architect/.env |
get_remote_control_info | Local URL + QR code for mobile remote |
capture_build_context | Return the latest Minecraft screenshot as a base64 image |
poll_mobile_commands | Check for commands queued from the mobile remote |
establish_architectural_style | Generate and save a style spec for a theme |
visualize_architectural_concept | Generate a concept image from a prompt + reference screenshot |
MCP resource: mcp://voxel-architect/style — the active architectural style spec (markdown).
MCP client config — npx method
{
"mcpServers": {
"voxel-architect": {
"command": "npx",
"args": ["-y", "@liquidmongoose/mcp-server"],
"env": {
"ARCHITECT_UNLOCK_KEY": "your-license-key-here"
}
}
}
}
MCP client config — Docker method
docker pull liquidmongoose/mcp-server:latest
{
"mcpServers": {
"voxel-architect": {
"command": "docker",
"args": ["run", "--rm", "-i", "-e", "ARCHITECT_UNLOCK_KEY=your-license-key-here", "liquidmongoose/mcp-server:latest"]
}
}
}
Docker variant does not support Live screen capture (headless container).
Supported MCP clients
Claude Desktop, Claude Code CLI, ChatGPT Desktop (Plus/Pro), Cursor, Windsurf, VS Code + Copilot, Cline, Gemini CLI, Zed, JetBrains AI Assistant.
Building distribution binaries
npm run package
Produces standalone binaries for macOS arm64, Linux x64, and Windows x64 via pkg. The dist/ directory is committed — binaries and bundle.js are shipping artifacts.
Staging — Cloudflare Access
Both staging URLs are gated by Cloudflare Access. Browser access requires email OTP. For scripts or MCP servers pointed at staging, set EXTRA_API_HEADERS in ~/.voxel-architect/.env:
EXTRA_API_HEADERS={"CF-Access-Client-Id":"<CF_ACCESS_CLIENT_ID>","CF-Access-Client-Secret":"<CF_ACCESS_CLIENT_SECRET>"}
Omitting these headers returns an HTML redirect from the access gate, not a JSON error.