Skip to main content
Glama
Vultr Codex MCP

Vultr Codex MCP

by heyzeyu

Vultr Codex Plugin

A Codex plugin for managing Vultr with explicit safety guards. The first version focuses on small VPS workflows: inspect account state, preview instance creation, then perform selected mutations only after exact confirmation.

The plugin's tools are implemented through a local MCP server, but the user-facing product is a Codex plugin.

Features

  • List Vultr account, instances, plans, regions, OS images, SSH keys, and firewall groups.

  • Check whether vultr-cli is available locally for optional manual workflows.

  • Preview instance creation before spending money.

  • Restrict instance creation by plan, region, and monthly cost.

  • Require exact confirmation strings for create, reboot, snapshot, and delete.

  • Read the Vultr token only from VULTR_API_KEY.

Related MCP server: SSH Linux Control

Quick Start

npm install
npm run verify
export VULTR_API_KEY="your-vultr-api-key"

The Codex plugin manifest is in .codex-plugin/plugin.json; the MCP configuration is in .mcp.json. The bundled server entrypoint is mcp/server.mjs.

Codex Plugin Install

During local development, keep the repository under:

/Users/zeyuwang/Documents/project/vultr-codex-plugin

Then install the plugin from a local marketplace entry or copy/symlink the repository into your personal plugin marketplace. The plugin does not need the Vultr token at install time, but Vultr API tools require VULTR_API_KEY in the environment where Codex launches the MCP server.

If you only want to smoke-test the MCP server without installing the plugin:

printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"smoke","version":"0.0.0"}}}' \
  '{"jsonrpc":"2.0","method":"notifications/initialized","params":{}}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
  | node ./mcp/server.mjs

Safety Policy

By default, create operations are limited to:

  • Plans: vc2-1c-1gb, vc2-1c-2gb, vc2-2c-2gb

  • Regions: nrt, itm, sgp, icn, lax, sjc, sea

  • Maximum monthly cost: $20

Override these with environment variables:

VULTR_ALLOWED_PLANS=vc2-1c-1gb,vc2-1c-2gb
VULTR_ALLOWED_REGIONS=nrt,sgp,lax
VULTR_MAX_MONTHLY_COST_USD=10

Confirmation Strings

Mutation tools reject calls unless the confirm field exactly matches the expected string returned by preview or described by the tool:

create:<label>:<plan>:<region>
reboot:<instance_id>
snapshot:<instance_id>
delete:<instance_id>:<label>

For deletion, the server first fetches the instance and checks that the Vultr label matches the provided label.

Tools

  • get_policy

  • get_account

  • get_vultr_cli_status

  • list_instances

  • get_instance

  • list_regions

  • list_plans

  • list_os

  • list_ssh_keys

  • list_firewall_groups

  • create_instance_preview

  • create_instance

  • reboot_instance

  • create_snapshot

  • delete_instance

Development

npm install
npm run check
npm test
npm run build

The source lives under src/. npm run build bundles it into mcp/server.mjs, which is what Codex launches.

Local Context

For this machine, the preferred code repository root is:

/Users/zeyuwang/Documents/project

Available Tools

15 tools
create_instanceCreate Vultr instanceA

Create a Vultr instance after policy validation and exact confirmation.

Inputs: plan (required), label (required), region (required), confirm (required), +11 more.

create_instance_previewcreate_instance_previewA
Read-onlyIdempotent

Validate and preview a Vultr instance creation request without charging money.

Inputs: plan (required), label (required), region (required), tags, +10 more.

create_snapshotCreate Vultr snapshotC

Create a Vultr snapshot after exact confirmation.

Inputs: confirm (required), description (required), instance_id (required).

delete_instanceDelete Vultr instanceA
Destructive

Delete a Vultr instance after fetching it, checking its label, and exact confirmation.

Inputs: label (required), confirm (required), instance_id (required).

get_accountget_accountA
Read-onlyIdempotent

Show Vultr account metadata.

Inputs: no named parameters.

get_instanceget_instanceA
Read-onlyIdempotent

Fetch one Vultr instance by id.

Inputs: instance_id (required).

get_policyget_policyA
Read-onlyIdempotent

Show the local safety policy.

Inputs: no named parameters.

get_vultr_cli_statusget_vultr_cli_statusA
Read-onlyIdempotent

Check whether a local vultr-cli binary is available. API tools do not require it.

Inputs: no named parameters.

list_firewall_groupslist_firewall_groupsA
Read-onlyIdempotent

List Vultr firewall groups.

Inputs: no named parameters.

list_instanceslist_instancesC
Read-onlyIdempotent

List Vultr instances in the account.

Inputs: tag, region.

list_oslist_osA
Read-onlyIdempotent

List Vultr operating system ids.

Inputs: no named parameters.

list_planslist_plansB
Read-onlyIdempotent

List Vultr plans. Set allowed_only to true to see plans permitted by policy.

Inputs: type, allowed_only.

list_regionslist_regionsA
Read-onlyIdempotent

List Vultr regions. Set allowed_only to true to see the policy allowlist.

Inputs: allowed_only.

list_ssh_keyslist_ssh_keysA
Read-onlyIdempotent

List Vultr SSH keys.

Inputs: no named parameters.

reboot_instanceReboot Vultr instanceA

Queue a Vultr instance reboot after exact confirmation.

Inputs: confirm (required), instance_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables complete Vultr cloud infrastructure management through natural language commands, providing 335+ tools across 27 services including compute, DNS, Kubernetes, databases, and networking. Features smart identifier resolution allowing users to reference resources by human-readable names instead of UUIDs.
      322
      27
      MIT
    • A
      license
      D
      quality
      D
      maintenance
      Enables safe, confirmable Proxmox operations: read-only cluster/guest status and bounded power actions and snapshot creation, with explicit byte-for-byte approval for each mutation.
      5
      MIT