Gessa: game asset generation for AI agents

ai.gessaPublished by gessa.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Generate game-ready 3D models, textures, and audio from natural language, over MCP.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Gessa lets an AI assistant generate game-ready 3D models, textures, and audio from natural-language prompts over MCP.

What you can do
  • Generate game-ready 3D models, textures, and audio from natural-language prompts.
  • Work through a hosted Gessa API, either as a remote connector or via a local stdio proxy package.
  • Use read and write scopes on the API key to control what the assistant can do.
When to use it
Useful when building or prototyping games and you want an assistant to produce 3D assets, textures, or sound effects from descriptions instead of sourcing them by hand.
Requirements
A Gessa API key (mcpkey_...) sent as a bearer Authorization header, or OAuth for remote connectors. A key can be minted anonymously through the provider's agent onboarding endpoint or by claiming a workspace. The stdio option runs through npx and needs Node.js; GESSA_API_URL can override the default API origin. Network access to the Gessa API is required.
Before you install
The server requires a secret API key or OAuth token; keep it out of shared configs. Keys carry read and write scopes, so the assistant may create or change assets in your workspace. Prompts and generated content are sent to Gessa's hosted service. The manifest lists no tools, so review what the assistant can actually do before granting write access.

Installation

In SourceWeft

  1. Open Gessa: game asset generation for AI agents in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/ai.gessa%2Fmcp-server/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gessa-game-asset-generation-for-ai-agent": {
      "type": "http",
      "url": "https://api.gessa.ai/mcp/rpc"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.