dc-corporations
by pipeworx-io
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTPS_PROXY | No | HTTPS proxy URL used by the npm stdio bridge when NODE_USE_ENV_PROXY=1 is set, since Node's built-in fetch does not read HTTPS_PROXY by default. | |
| PIPEWORX_API_KEY | No | Optional Pipeworx API key for the npm stdio bridge (@pipeworx/mcp-dc-corporations). Without a key it calls anonymously, capped at 50 calls a day; a free account raises that to 200 a day. The key is sent as a Bearer token, so calls are metered and billed the same way as a hosted connection. | |
| NODE_USE_ENV_PROXY | No | Set to 1 so that newer Node releases make the built-in fetch honour HTTPS_PROXY when running the npm stdio bridge behind an HTTPS proxy; check your Node version's documentation. | |
| 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 the npm bridge lists only this pack's tools. |
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