lucky-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUCKY_BASE_URL | Yes | The base URL of the Lucky instance (e.g., https://lucky.example.com:16601). | |
| LUCKY_OPEN_TOKEN | Yes | Your 32-character Lucky OpenToken. | |
| LUCKY_TLS_VERIFY | No | Set to 'false' to disable TLS certificate verification (e.g., for self-signed certificates). | true |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lucky_statusA | Read the Lucky version, system information, and enabled module list. |
| lucky_api_catalogA | List APIs discovered from the Lucky 3.0.0 web frontend. Filter by module or side-effect level before using lucky_api_call. |
| lucky_api_describeA | Describe one cataloged Lucky endpoint by catalog id. |
| lucky_api_callA | Call any API present in the versioned catalog. Arbitrary URLs are rejected. Account, password, and OpenToken mutations are blocked in code; all other Lucky functions are available. |
| lucky_list_port_forwardsA | List Lucky port forward objects. |
| lucky_create_port_forwardC | Create a Lucky port forward using the native Lucky JSON object. |
| lucky_update_port_forwardB | Update a Lucky port forward using its key and complete native Lucky JSON object. |
| lucky_delete_port_forwardB | Delete a Lucky port forward by key. |
| lucky_list_web_servicesA | List Lucky web service objects. |
| lucky_create_web_serviceC | Create a Lucky web service using the native Lucky JSON object. |
| lucky_update_web_serviceB | Update a Lucky web service using its key and complete native Lucky JSON object. |
| lucky_delete_web_serviceA | Delete a Lucky web service by key. |
| lucky_list_ddnssA | List Lucky ddns objects. |
| lucky_create_ddnsC | Create a Lucky ddns using the native Lucky JSON object. |
| lucky_update_ddnsA | Update a Lucky ddns using its key and complete native Lucky JSON object. |
| lucky_delete_ddnsB | Delete a Lucky ddns by key. |
| lucky_list_certificatesA | List Lucky certificate objects. |
| lucky_create_certificateB | Create a Lucky certificate using the native Lucky JSON object. |
| lucky_update_certificateB | Update a Lucky certificate using its key and complete native Lucky JSON object. |
| lucky_delete_certificateB | Delete a Lucky certificate by key. |
| lucky_list_stun_rulesA | List Lucky stun rule objects. |
| lucky_create_stun_ruleC | Create a Lucky stun rule using the native Lucky JSON object. |
| lucky_update_stun_ruleC | Update a Lucky stun rule using its key and complete native Lucky JSON object. |
| lucky_delete_stun_ruleB | Delete a Lucky stun rule by key. |
| lucky_get_settingsA | Read Lucky base settings. Secret values are always redacted. |
| lucky_update_settingsA | Merge a partial patch into Lucky base settings while preserving and prohibiting changes to the admin account, admin password, and OpenToken fields. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Each resource type has a clearly separated CRUD set, and settings/status/API catalog tools serve distinct purposes. The main ambiguity is lucky_api_call, which can theoretically overlap with the explicit CRUD tools, but it is framed as a generic catalog-driven escape hatch.
The lucky_ prefix and snake_case convention are consistent, and most tools follow a verb_noun pattern like list/create/update/delete. Minor deviations exist: lucky_status uses a bare noun instead of get_status, and api_catalog/api_describe are not perfectly parallel with list/describe verbs.
At 26 tools this is heavier than the typical well-scoped server, but the count is justified by applying the same CRUD pattern across five resource types plus settings, status, and API discovery tools. The tools are not redundant or padded; the breadth comes from the domain.
The server provides full list/create/update/delete coverage for certificates, stun rules, port forwards, web services, and DDNS, plus settings read/update, status, and an API catalog escape hatch. This covers the apparent Lucky management lifecycle without obvious dead ends.