OVHcloud MCP server

What the model can do

OVHcloud hosting: the account, bills with amounts, Public Cloud projects with their instances (status, region, flavor, IPs) and current-month usage cost, VPS, dedicated servers (datacenter, power, state, OS), and DNS zones with their records; when you ask, can reboot, start or stop a cloud instance or a VPS, reboot a dedicated server, and create, change or delete DNS records and publish a zone's changes.

Reads

• ovhcloud_accountThe OVHcloud account: customer id (nichandle), organisation, country, currency, OVH subsidiary and legal form.
• ovhcloud_billsOVHcloud bills in a date range (default the last 90 days), newest first: id, date, category, order, total with and without tax, and tax.
• ovhcloud_cloud_projectsOVHcloud Public Cloud projects: project id, name, description, status, plan, creation and expiry dates.
• ovhcloud_instancesInstances in an OVHcloud Public Cloud project: id, name, status (ACTIVE, SHUTOFF, ERROR…), region, flavor, image, IP addresses…
• ovhcloud_cloud_usageCurrent-month usage of an OVHcloud Public Cloud project so far: the period, when it was last updated, the total price, and the cost per resource type.
• ovhcloud_vpsOVHcloud VPS: name, display name, state (running, stopped, rebooting…), zone, offer and model, vCores, memory and disk, and whether locked.
• ovhcloud_dedicated_serversOVHcloud dedicated servers: name, datacenter and region, IP and reverse, OS, power state, state, commercial range, support level and monitoring.
• ovhcloud_dnsOVHcloud DNS: with no zone, the zones on the account; with a zone, its records (id, type, subdomain, target, TTL)…

Acts, when you ask

These change something in OVHcloud. 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.

• ovhcloud_reboot_instanceReboots an OVHcloud Public Cloud instance: soft asks the operating system to restart, hard power-cycles it like pulling the plug.
• ovhcloud_start_instanceStarts a stopped OVHcloud Public Cloud instance.
• ovhcloud_stop_instanceStops an OVHcloud Public Cloud instance: whatever runs on it goes down until it is started again.
• ovhcloud_reboot_vpsReboots an OVHcloud VPS; it is down until it comes back.
• ovhcloud_start_vpsPowers on a stopped OVHcloud VPS.
• ovhcloud_stop_vpsPowers off an OVHcloud VPS: it is down until started again.
• ovhcloud_reboot_serverReboots an OVHcloud dedicated server (a hardware reset); it is down until it comes back.
• ovhcloud_create_dns_recordAdds a record to an OVHcloud DNS zone.
• ovhcloud_update_dns_recordChanges a record in an OVHcloud DNS zone: its target, and optionally subdomain and TTL.
• ovhcloud_delete_dns_recordPermanently deletes a record from an OVHcloud DNS zone; it stops resolving once the zone is refreshed.
• ovhcloud_refresh_dns_zoneRefreshes an OVHcloud DNS zone, publishing every pending record change in it to OVHcloud's name servers and so to the world.

Connect it

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

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

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

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

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 OVHcloud 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 has this month's Public Cloud usage cost so far?
• › Which instances are shut off or in error?
• › What were our last three OVHcloud bills?
• › What records are in the acme.co.uk DNS zone?
• › Reboot the staging VPS.

Questions

Is this an official OVHcloud MCP server?

No. It is Memtro's MCP server with Memtro's OVHcloud connector behind it: the connector reads OVHcloud through its API with the credentials you connect on Dashboard → Connections, and OVHcloud 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 OVHcloud?

Only when you ask, and only what it has been granted: reboot a Public Cloud instance (soft or hard); start a stopped Public Cloud instance; stop a Public Cloud instance; reboot a VPS; start a VPS; stop a VPS; reboot a dedicated server; create a DNS record; change a DNS record's target, subdomain or TTL; delete a DNS record; publish a DNS zone's pending changes. 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.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server