@pipeworx/france-legi
by pipeworx-io
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIPEWORX_API_KEY | No | Optional Pipeworx API key for the local npm stdio bridge (`npx -y @pipeworx/mcp-france-legi`). Without a key it calls anonymously, capped at 50 calls a day; a free account key raises that to 200 a day. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there. | |
| NODE_USE_ENV_PROXY | No | Set to `1` so newer Node releases honour `HTTPS_PROXY`, for running the npm bridge behind an HTTPS proxy; Node's built-in `fetch` does not read `HTTPS_PROXY` by default. | |
| PIPEWORX_META_TOOLS | No | Set to `1` to also list `ask_pipeworx` and the other gateway-wide tools. The npm bridge lists only this pack's tools by default. |
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