Luceed MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSH_ENABLED | No | Whether to open a local SSH forward for an IP-whitelisted Luceed instance. | |
| MCP_HTTP_PATH | No | The unguessable HTTP path for the MCP endpoint, e.g. `/mcp-a8f3…`. | |
| MCP_TRANSPORT | No | The MCP transport to use: `stdio` (default) or `http`. | |
| MCP_AUTH_TOKEN | No | Bearer / `X-API-Key` token required when using HTTP transport. | |
| LUCEED_BASE_URL | Yes | The Luceed API base URL. Must include `/datasnap/rest/`. | |
| LUCEED_PASSWORD | Yes | Luceed API password (HTTP Basic auth). | |
| LUCEED_USERNAME | Yes | Luceed API username (HTTP Basic auth; prefer a read-only user). |
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