forge3d-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORGE3D_WORKDIR | No | Absolute path to the working directory used by the forge3d MCP server for outputs (models, viewers, job records). | |
| FORGE3D_EXEC_MODE | No | Set to 'subprocess' to run agent code in a killable child process with rlimits instead of inside the server (HTTP mode forces subprocess isolation). | |
| FORGE3D_THREE_URL | No | URL of a local mirror of three.js used when building the single-file viewer page, for air-gapped machines (defaults to a CDN). | |
| FORGE3D_HTTP_TOKEN | No | Bearer token required by the HTTP transport for any non-loopback bind (e.g. set via openssl rand -hex 32). The server refuses a public bind without a token. | |
| FORGE3D_ALLOW_CODE_EXEC | No | Set to false to disable execution of agent-written code by the procedural, cadquery and blender backends. |
Instructions
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.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues