Layergen Mcp

io.github.adebayojuwon200-pixelPublished by GitHub account adebayojuwon200-pixelv0.3.1Updated Oct 24, 2026

Layergen 3D model generation, retexture, and repair — for Claude Desktop and any MCP host.

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

Layergen MCP lets an assistant generate, retexture and repair 3D models through the Layergen service from a local MCP host such as Claude Desktop.

What you can do
  • Generate 3D models through the Layergen service
  • Retexture existing 3D models
  • Repair 3D models
  • No individual tools are listed in the manifest, so the exact operations are not documented here; the description names generation, retexture and repair only.
When to use it
Worth adding when you want an assistant to produce or fix 3D assets for a project without leaving the chat, and you already use or are willing to sign up for Layergen.
Requirements
Runs locally over stdio via npx from the npm package @layergen/mcp, so Node.js is needed. Requires a Layergen API key in the LAYERGEN_API_KEY environment variable, created in the Layergen app settings. Network access to the Layergen API is required; LAYERGEN_API_URL can override the base URL. Desktop host only.
Before you install
The server needs a Layergen API key, which is a billable account credential; check Layergen's pricing and usage limits before generating assets. Model generation, retexture and repair send your prompts and any source models to Layergen's servers, a third party. LAYERGEN_API_URL can point the server at a different endpoint, so only change it to a host you trust.

Installation

In SourceWeft

  1. Open Layergen Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.3.1LatestOct 11, 2026
  2. v0.3.0Sep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.