Dockge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATE_DIR | No | State directory for local source execution, e.g., ./data. Use one bridge process per state directory. | ./data |
| MCP_BEARER_TOKEN | Yes | A separate MCP bearer token, for example generated with openssl rand -hex 32. Required for authenticating MCP hub/client connections. | |
| MCP_ALLOWED_HOSTS | No | The exact host and port used by the hub, e.g., 127.0.0.1:3000. Retain 127.0.0.1:3000 for image health checks. Required for external hub access. | |
| DOCKGE_ALLOW_WRITE | No | Enable stack writes (create, edit, deploy, start, stop, restart, update, down). Disabled by default. | false |
| DOCKGE_ALLOW_DELETE | No | Enable stack deletion. Disabled by default. | false |
| MCP_ALLOWED_ORIGINS | No | Exact origin entry for browser clients. No browser CORS preflight is implemented initially; the supported client is a server-side hub. | |
| DOCKGE_ALLOWED_AGENTS | No | Optionally restricts accessible agents. Clients cannot provide arbitrary upstream URLs. | |
| DOCKGE_ALLOW_ENV_READ | No | Enable environment reads. Disabled by default. | false |
| DOCKGE_ALLOW_ENV_WRITE | No | Enable environment writes. Disabled by default. | false |
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