Schema | Goxel-MCP

Goxel-MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
`GOXEL_APP`	No	Official Goxel app (used with `live: false`).	/Applications/goxel.app
`GOXEL_REF`	No	Used by `scripts/build-goxel.sh`: the Goxel revision to build.
`GOXEL_SRC`	No	Used by `scripts/build-goxel.sh`: path to existing Goxel sources instead of cloning them into `goxel-src/`.
`GOXEL_REPO`	No	Used by `scripts/build-goxel.sh`: the Goxel repository to clone.
`GOXEL_MCP_SOCKET`	No	Path of the bridge socket. Goxel opens the socket only when it is started with `--mcp-socket` or this environment variable.
`GOXEL_MCP_GOXEL_BIN`	No	Goxel build with the bridge.	goxel-build/goxel
`GOXEL_MCP_LOG_LEVEL`	No	Log level: `debug`, `info`, `warn` or `error`. Logs go to stderr; stdout is only used by the MCP protocol.	info
`GOXEL_MCP_WORKSPACE`	No	The workspace is the only folder the server reads and writes. Your models, exports and previews go there, and the server keeps its backups and the bridge socket in `<workspace>/.goxel-mcp/`. When the variable is not set, the current directory is used.	current directory
`GOXEL_MCP_SKIP_GOXEL`	No	Set to `1` to skip the tests that use the Goxel build (validation, glTF export, live editing).

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo issues