lunanode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUNANODE_API_ID | Yes | Your LunaNode API ID. | |
| LUNANODE_API_KEY | Yes | Your LunaNode API key (128 characters). | |
| LUNANODE_ENABLE_WRITES | No | Enables write-tier tools. Unset = off. true/1 = all write tools. Comma-separated tool names = only those tools. | |
| LUNANODE_ENABLE_DELETES | No | Enables delete-tier tools. Unset = off. true/1 = all delete tools. Comma-separated tool names = only those 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
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 |
|---|---|
| vm_listA | List all virtual machines on the LunaNode account. |
| vm_infoA | Get detailed configuration and live status for a virtual machine. |
| vm_iplistA | List all IP addresses assigned to a virtual machine. |
| image_listA | List images available to the account, optionally filtered by region. |
| image_detailsA | Get metadata for a specific image. |
| volume_listA | List block storage volumes, optionally filtered by region. |
| volume_infoA | Get details for a specific volume. |
| volume_snapshot_listB | List volume snapshots in a region. |
| floating_ip_listA | List all floating IPs on the account. |
| ssh_key_listA | List stored SSH public keys with their IDs. |
| plan_listA | List available LunaNode VM plans with pricing, CPU, RAM, storage, and regional availability. |
| region_listA | List all LunaNode regions where services can be deployed. |
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 12 tools
Each tool targets a distinct resource and action, such as listing all VMs vs. getting details for a single VM vs. listing IPs. There is no overlap or ambiguity in what each tool returns.
All tools follow a consistent snake_case pattern of resource-based nouns with descriptive suffixes like _list, _info, and _details. Minor variations such as vm_iplist vs. volume_snapshot_list do not break the overall predictability.
12 tools is well-scoped for an infrastructure read-only API, covering VMs, images, volumes, snapshots, IPs, SSH keys, plans, and regions without unnecessary bloat.
The server is entirely read-only, providing only list and info operations. There are no create, update, delete, or action tools, which is a significant gap for a cloud management MCP server. Users can inspect resources but cannot manage them.