engine v1.0.222generated projectionGenerated 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.

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.

Source of truth: docs/creator/mcp/introduction.md in the engine repo. This page is rendered by rune_web from a version-pinned docs export; do not edit generated docs content here.