Vultr Codex MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VULTR_API_KEY | Yes | Your Vultr API key | |
| VULTR_ALLOWED_PLANS | No | Comma-separated list of allowed plans (e.g., vc2-1c-1gb,vc2-1c-2gb) | |
| VULTR_ALLOWED_REGIONS | No | Comma-separated list of allowed regions (e.g., nrt,sgp,lax) | |
| VULTR_MAX_MONTHLY_COST_USD | No | Maximum monthly cost in USD (e.g., 10) |
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 |
|---|---|
| get_policyA | Show the local safety policy. |
| get_accountA | Show Vultr account metadata. |
| get_vultr_cli_statusA | Check whether a local vultr-cli binary is available. API tools do not require it. |
| list_instancesC | List Vultr instances in the account. |
| get_instanceA | Fetch one Vultr instance by id. |
| list_regionsA | List Vultr regions. Set allowed_only to true to see the policy allowlist. |
| list_plansB | List Vultr plans. Set allowed_only to true to see plans permitted by policy. |
| list_osA | List Vultr operating system ids. |
| list_ssh_keysA | List Vultr SSH keys. |
| list_firewall_groupsA | List Vultr firewall groups. |
| create_instance_previewA | Validate and preview a Vultr instance creation request without charging money. |
| create_instanceA | Create a Vultr instance after policy validation and exact confirmation. |
| reboot_instanceA | Queue a Vultr instance reboot after exact confirmation. |
| create_snapshotC | Create a Vultr snapshot after exact confirmation. |
| delete_instanceA | Delete a Vultr instance after fetching it, checking its label, and exact confirmation. |
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 15 tools
Each tool targets a distinct action on a specific resource (e.g., create_instance vs. create_snapshot, list_instances vs. list_os). No two tools have overlapping purposes, and even closely related tools like create_instance and create_instance_preview are clearly differentiated by the preview aspect.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_instance, list_firewall_groups). The naming is predictable and uniform across the entire set, with no mixing of conventions.
With 15 tools, the server covers core Vultr management operations without being bloated. Each tool serves a clear purpose, and the count feels well-scoped for the domain.
The tool set covers instance creation, reading, deletion, reboot, and preview, plus listing of resources like SSH keys, OS, plans, and regions. However, there are notable gaps: no instance update or resize, no snapshot listing or deletion, no SSH key creation/deletion, and no firewall rule management. This leaves several common workflows incomplete.