Telegram Channels
by pipeworx-io
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTPS_PROXY | No | HTTPS proxy to use when running the npm stdio bridge behind a proxy. Node's built-in fetch does not read it by default; newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set. | |
| PIPEWORX_API_KEY | No | Optional API key for a free Pipeworx account (get one at https://pipeworx.io/signup). Without a key, calls are anonymous and capped at 50 calls a day; with a key the cap is 200 calls a day. Sent as a Bearer token. | |
| NODE_USE_ENV_PROXY | No | Set this (e.g. to 1) so newer Node releases honour HTTPS_PROXY in Node's built-in fetch when running the npm stdio bridge behind an HTTPS proxy. | |
| PIPEWORX_META_TOOLS | No | Set to 1 to also list ask_pipeworx and the other gateway-wide (meta) tools alongside this pack's tools. By default only this pack's tools are listed. |
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