Is this an official Vultr MCP server?

No. It is Memtro's MCP server with Memtro's Vultr connector behind it: the connector reads Vultr through its API with the credentials you connect on Dashboard → Connections, and Vultr publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Vultr?

Only when you ask, and only what it has been granted: start a Vultr instance; halt (power off) a Vultr instance; reboot a Vultr instance; delete a Vultr instance permanently; take a snapshot of a Vultr instance; delete a Vultr snapshot permanently; add a DNS record to a Vultr-hosted domain; change a DNS record on a Vultr-hosted domain; delete a DNS record from a Vultr-hosted domain. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

Vultr MCP server

Vultr in any MCP client, through Memtro: Vultr does not publish this server. Memtro's Vultr connector reads Vultr through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Vultr: cloud instances with plan, region, IPs, power and status, bare-metal servers, Kubernetes clusters and node pools, DNS domains and their records, and snapshots. Can start, halt, reboot or delete an instance, take or delete a snapshot, and add, change or delete a DNS record.

Reads

vultr_list_instancesVultr cloud instances: label, hostname, status and power, region, plan, OS, vCPUs, RAM, disk, IPv4 and IPv6, tags and created date.
vultr_list_bare_metalsVultr bare-metal servers: label, status and power, region, plan, OS, CPUs, RAM, disk, IPs, tags and created date.
vultr_list_kubernetes_clustersVultr Kubernetes Engine clusters: label, status, Kubernetes version, region, API endpoint, whether the control plane is HA, and node pools with plan…
vultr_list_domainsDNS domains hosted on Vultr, with whether DNSSEC is on and the date added.
vultr_list_dns_recordsDNS records of one Vultr-hosted domain: type, name, data (the address or target), priority and TTL.
vultr_list_snapshotsSnapshots on the Vultr account: description, status, size and compressed size, and created date.

Acts, when you ask

These change something in Vultr. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

vultr_start_instanceStarts a Vultr instance (and restarts it if it is already running).
vultr_halt_instanceHalts (powers off) a Vultr instance, taking it offline for its users until started again.
vultr_reboot_instanceReboots a Vultr instance; it is briefly offline.
vultr_delete_instancePermanently destroys a Vultr instance and its disk; it cannot be undone except from a snapshot taken beforehand.
vultr_create_snapshotTakes a snapshot of a Vultr instance's disk, billed for storage each month until deleted.
vultr_delete_snapshotPermanently deletes a Vultr snapshot; it cannot be undone.
vultr_create_dns_recordAdds a DNS record to a Vultr-hosted domain.
vultr_update_dns_recordChanges a DNS record on a Vultr-hosted domain (its name, data, TTL or priority; the type cannot change).
vultr_delete_dns_recordDeletes a DNS record from a Vultr-hosted domain; the name stops resolving to it for everyone once caches expire.

Connect it

First connect Vultr on Dashboard → Connections, then add Memtro to your client once. The Vultr tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Vultr connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What instances are running in Frankfurt, and on which plans?
› Where does api.acme.com point?
› Which Kubernetes clusters are on an older version?
› Is DNSSEC on for all our Vultr domains?
› Point status.acme.com at 203.0.113.40

Questions

Is this an official Vultr MCP server?: No. It is Memtro's MCP server with Memtro's Vultr connector behind it: the connector reads Vultr through its API with the credentials you connect on Dashboard → Connections, and Vultr publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Vultr?: Only when you ask, and only what it has been granted: start a Vultr instance; halt (power off) a Vultr instance; reboot a Vultr instance; delete a Vultr instance permanently; take a snapshot of a Vultr instance; delete a Vultr snapshot permanently; add a DNS record to a Vultr-hosted domain; change a DNS record on a Vultr-hosted domain; delete a DNS record from a Vultr-hosted domain. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.