Asset Auto Generator

io.github.TranThienTrongPublished by GitHub account TranThienTrongv1.0.0Updated Oct 24, 2026

An MCP server that provides asset auto generator

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

A remote MCP server named Asset Auto Generator that is described only as providing asset auto generation, with no documented tools or usage details.

What you can do
The available material gives almost no functional detail. The registry describes it only as an MCP server that provides asset auto generation, and the README contains just a title and an internal package name. No tools, parameters, or supported asset types are listed, so what an assistant could actually do with it cannot be determined from this listing.
When to use it
Only worth considering if you specifically need automated asset generation and are willing to test an undocumented remote endpoint to discover its capabilities. For most users, the lack of tool documentation makes it hard to justify over a better-described alternative.
Requirements
It runs as a remote streamable HTTP endpoint at a GitHub Pages address, so network access is needed. No authentication, environment variables, headers, or packages are declared, and no local runtime is required.
Before you install
The server is essentially undocumented: no tools, inputs, or outputs are described, so behavior is unknown before connecting. It is hosted on GitHub Pages and declares no authentication, so avoid sending sensitive data. Any generated assets and where they are stored or sent are not explained.

Installation

In SourceWeft

  1. Open Asset Auto Generator in the dashboard and add it to a workspace.
  2. 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/io.github.TranThienTrong%2Fasset-auto-generator/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "asset-auto-generator": {
      "type": "http",
      "url": "https://tranthientrong.github.io/mcp/asset-auto-generator"
    }
  }
}

README

MCP Asset Generator Server

mcp-name=io.github.TranThienTrong/mcp_asset-generator

Source: README.md at commit ba13510

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.