PteroOps
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PTEROOPS_CONFIG | No | Path to a PteroOps configuration file (e.g., pteroops.config.yaml) that contains all settings. | |
| PTERO_HTTP_TOKEN | No | Token for HTTP transport authentication. Required when using --transport http off-loopback. | |
| PTERO_DEFAULT_PANEL | No | Name of the default panel (e.g., 'prod'). Optional if only one panel is configured. | |
| PTERO_PANEL_PROD_URL | No | URL of the Pterodactyl panel (e.g., https://panel.example.com). | |
| PTERO_PANEL_PROD_CLIENT_KEY | No | Client API key (ptlc_...) for the panel. |
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