Skip to main content
Glama
gessa-ai

ai.gessa/mcp-server

Official
README.md
# @gessa/mcp-server

mcp-name: ai.gessa/mcp-server

Generate game-ready 3D models, textures, and audio from natural language —
**zero configuration**. No account, no signup, no API key: on first run the
proxy provisions itself a free Gessa agent workspace (25 free models/month)
and persists the credential locally. The only MCP server that sets itself up.

```json
{
  "mcpServers": {
    "gessa": {
      "command": "npx",
      "args": ["-y", "@gessa/mcp-server"]
    }
  }
}
```

That is the whole setup. 205 tools: generation (text→3D model on Gessa's
premium Hunyuan3D lane, images, textures, audio), plus the full Gessa game
engine surface (worlds, scripting, prefabs, multiplayer deploys).

Have a key already? Set `GESSA_API_KEY` and it wins unconditionally — the
network is never touched for provisioning. Other env vars: `GESSA_API_URL`
(default `https://api.gessa.ai`), `GESSA_STATE_DIR` (credential location,
default `~/.gessa`), `GESSA_AGENT_NAME` (name your workspace).

The package does not run engine logic locally. It starts an SDK stdio MCP server, mirrors the remote Gessa tool/resource/prompt surface through the SDK Streamable HTTP client, and authenticates to `/mcp/rpc` with `GESSA_API_KEY`.

## Release

Initial npm release: `0.1.0`.

Publish by tagging the repo with the package version:

```bash
git tag mcp-server-v0.1.0
git push origin mcp-server-v0.1.0
```

The publish workflow verifies the tag matches `packages/mcp-server/package.json`, builds the workspace, runs an npm pack dry-run, and publishes `@gessa/mcp-server` with npm provenance.

## Version Sync Policy

Keep the package version synchronized with the engine MCP API it proxies. Any change that alters `/mcp/rpc` authentication semantics, tool/resource/prompt names, required input schemas, or response shapes must update this package and the engine MCP docs in the same PR.

Use patch bumps for proxy-only fixes that do not change the remote MCP contract. Use minor bumps for additive MCP surface changes or authentication/client behavior changes. Reserve major bumps for breaking changes to the remote MCP contract.