Gessa Docs
Generated Reference

Reference

Gessa MCP

Gessa exposes engine capabilities as MCP tools for creator agents. The remote transport is Streamable HTTP at /mcp/rpc; local subprocess clients use @gessa/mcp-server, a thin SDK stdio proxy to that endpoint.
engine v1.0.234Copy for LLM

Use MCP when an agent needs to create or inspect workspaces, games, project graph resources, scripts, warehouse data, generation jobs, deployments, runtime rooms, or engine capability metadata.

Do not pass MCP bearer tokens to downstream APIs. Gessa validates the MCP credential at the resource-server boundary and then calls canonical services with a derived principal.

Was this helpful?Report an issueContact support