@pipeworx/ats-boards
Officialby pipeworx-io
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTPS_PROXY | No | HTTPS proxy URL to use when running behind a proxy; requires NODE_USE_ENV_PROXY=1. | |
| PIPEWORX_API_KEY | No | Optional Pipeworx API key sent as a Bearer token. Without it calls are anonymous and capped at 50/day; a free account key raises the cap to 200/day. | |
| NODE_USE_ENV_PROXY | No | Set to 1 behind an HTTPS proxy so Node's built-in fetch honors HTTPS_PROXY. | |
| PIPEWORX_META_TOOLS | No | Set to 1 to also list ask_pipeworx and the other gateway-wide meta-tools on the local stdio bridge. |
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 recent community issues