For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/en/guides/web-cloud/domains/mcp-domain-getting-started.md.

Getting started with the MCP server for domain names

View as Markdown

Connect an AI agent to the OVHcloud MCP server to manage your domain names, DNS records and redirections in plain language

Info

The OVHcloud MCP server is under active development. The list of available tools grows regularly, so a capability missing today may be available shortly after. Check the OVHcloud MCP hub for the current inventory.

Objective

The Model Context Protocol (MCP) is an open standard that lets an AI assistant use external tools. The OVHcloud MCP server exposes your OVHcloud services as such tools, so an assistant can read and change your configuration on your behalf.

In practice, this means you can stop clicking through interfaces or writing API calls, and simply ask:

List my domain names and tell me which ones expire in the next 60 days.

This guide explains how to connect an AI agent to the OVHcloud MCP server and use it to manage your domain names, DNS records and redirections.

Requirements

  • Access to the
  • One supported MCP client installed (see Connect your agent)
  • A browser, to complete the OAuth2 login step

Instructions

1 — How MCP works

Three components are involved:

ComponentRole
Your AI agentThe assistant you talk to (a terminal agent, an IDE chat, your own application)
The OVHcloud MCP serverPublishes the available tools and executes them against your account
Your OVHcloud accountThe permissions, checked on every call, that decide what the agent may do

You never call a tool by name yourself. You describe what you want, the agent picks the matching tool, and it asks you to confirm before anything is modified.

Warning

An AI agent connected to MCP acts with your permissions. Read every confirmation prompt before accepting it, especially for operations that delete records or change name servers.

2 — The OVHcloud MCP hub

The OVHcloud MCP hub lists the services exposed as MCP tools and is the reference for what is currently available.

Pick the URL matching the region of your OVHcloud account:

RegionMCP server URL
Europehttps://mcp.eu.ovhcloud.com/mcp/{section}
Canadahttps://mcp.ca.ovhcloud.com/mcp/{section}

Replace {section} with the name of the section you want to connect to, as shown on the hub cards. You always connect to a specific section: there is no global URL exposing every tool at once.

Domain sections

Two sections cover domain names, one per API version:

SectionExposes
v1_domainThe API v1 domain tools
v2_domainThe API v2 domain tools

So the URL to use is https://mcp.eu.ovhcloud.com/mcp/v1_domain for a European account on API v1.

As things stand, API v1 remains the most feature-complete, so v1_domain exposes a wider tool set than v2_domain. API v2 is being expanded over time.

To understand what sets API v2 apart from API v1, read the OVHcloud API v2 - Principles of operation guide.

You can add either one, or both at the same time. v1_domain on its own is enough for every task in this guide.

3 — Connect your agent to MCP

Authentication uses OAuth2: the first time your agent contacts the server, a browser window opens on the OVHcloud login page. Once you have logged in, the agent reuses that session for its MCP calls.

Info

No custom HTTP header is required: the OAuth2 flow provides the credentials. OVHcloud's setup instructions specify leaving the headers section of your client configuration empty.

SHAI
Goose
Claude Code

SHAI is the OVHcloud terminal agent. Version 0.1.5 or higher is required.

Create the following configuration file, using the .ovh.config template from the SHAI repository:

$HOME/.config/shai/agents/ovh.config

Declare one entry under tools.mcp per section you want to use. This example enables both API versions:

{
  "name": "ovh",
  "description": "OVH agent with OVH MCP server for cloud management and API calls",
  "tools": {
    "builtin": ["*"],
    "builtin_excluded": [],
    "mcp": {
      "v1_domain": {
        "config": {
          "type": "http",
          "url": "https://mcp.eu.ovhcloud.com/mcp/v1_domain"
        },
        "enabled_tools": ["*"]
      },
      "v2_domain": {
        "config": {
          "type": "http",
          "url": "https://mcp.eu.ovhcloud.com/mcp/v2_domain"
        },
        "enabled_tools": ["*"]
      }
    }
  },
  "system_prompt": "{{CODER_BASE_PROMPT}}",
  "max_tokens": 4096,
  "temperature": 0.3
}

Replace the endpoints with those of your region.

Info

Do not add any credential to this file by hand. After you sign in, SHAI writes an access_token and an expires_at into each server's config block itself. Those values are personal secrets: never commit this file, and never share it as-is.

Then start the agent. Your browser opens on the OVHcloud login page; log in to complete the connection.

To confirm the connection works, ask your agent a read-only question:

List my OVHcloud domain names.

4 — Display information about a domain name

Start by listing your domains, then request the details of one of them.

Example request:

Show me the details of mydomain.ovh: expiry date, name servers and whether the transfer lock is on.

5 — Order a domain name

Ordering a domain name is done with the order-new-domain-name tool, available in the v1_domain section.

Example request:

Order mydomain.ovh for one year.

Before buying anything, ask for a simulation. The tool accepts a dryRun parameter: set to true, it checks the name's availability and calculates the price without committing to or billing anything.

Simulate the order of mydomain.ovh for one year.

Your agent then displays the quote — price, duration and the configuration that will be applied to the domain — and waits for your approval before going any further.

Once you approve the quote, the agent runs the call again with dryRun set to false. The order is then firm: the API returns the order form URL. Your agent hands you that URL directly in its answer: open it in your browser to pay for the order. You will also find this order form in the OVHcloud Control Panel, under .

Info

The order form must be paid for the registration to be sent to the registry. Your agent cannot pay on your behalf: follow the order form URL it returned to complete the payment. Until that payment is settled, the domain name remains available to someone else.

Warning

Confirming the order generates a real, billable order form on your OVHcloud account. Read the confirmation your agent asks for before accepting it, and check the domain name and the duration: a registration cannot be undone like a configuration change.

6 — Modify a DNS record

Related tools: create-domain-zone-record to add a record, delete-domain-zone-record to remove one, and get-domain-zone-details to inspect the zone.

Example requests:

Change the A record of www.mydomain.ovh to 203.0.113.42.

You do not need to know which type of record to change. Describe the outcome you want: your agent works out which record is involved, explains what it is about to change and waits for your approval before applying it.

My website is now hosted on a server whose IP address is 203.0.113.42.
Make www.mydomain.ovh point to it.
Warning

A modified DNS record only becomes active once the zone has been refreshed. If you omit that step, your change is saved but never applied. Ask your agent explicitly to refresh the zone, or check that it did.

Propagation across the internet can then take up to 24 hours, depending on the TTL of the record.

7 — Create a redirection

A redirection sends visitors from your domain to another address.

Example request:

Redirect blog.mydomain.ovh to https://mydomain.ovh/news, keeping the address visible in the browser.

8 — What else is covered

The v1_domain and v2_domain sections expose the matching OVHcloud API routes as tools: any operation you can perform on your domain names through the API is also available through MCP. Beyond the tasks above, this covers for example:

  • DNSSEC: enable, disable, and manage DS records
  • Transfer protection: lock and unlock
  • Contact management: owner, administrative, technical and billing
  • Name servers and glue records
  • DynHost (dynamic DNS) logins and records
  • Zone backup, restore, import and export
  • Task management: acceleration, cancellation, relaunch
  • AuthInfo code retrieval and outgoing transfer approval

If you are unsure whether an operation is possible, ask your agent to explain what it can do with your domain names.

Go further

Order a Domain Name with the OVHcloud API

Configure the DNS of your Domain Name

Redirecting a domain name managed by OVHcloud

AI Endpoints - Model Context Protocol (MCP) with LangChain4j

Information regarding OVHcloud service administration and how to find appropriate assistance

When using OVHcloud guides, please be aware of the following conditions:

  • User instructions aim to provide as many details as possible but cannot cover individual use cases. You might need to adapt the pertinent actions to your requirements.
  • The OVHcloud ecosystem is built for flexibility and freedom of choice. Customers are therefore responsible for the secure and proper configuration of their services. To prevent data loss, we strongly recommend to apply backup strategies to all your important data.
  • Our guides and tutorials may reference third-party software or services in combination with OVHcloud solutions. The technical support provided by OVHcloud does not include the configuration of systems or products outside of our responsibility. This includes but is not limited to:
    • Operating systems and user interfaces (Windows, Debian, Plesk, etc.).
    • Any other third-party software (FTP clients, email software, etc.).
    • Services offered by other providers (DNS, APIs, user interfaces, etc.).

To receive the appropriate assistance for any issues you might experience, follow these guidelines:

  • You seek personalized advice or you would like to discuss a topic that is not covered in detail by our documentation?
    Join the OVHcloud Community to search for your topic and reach out to other users.
  • You need to report an incident regarding your OVHcloud service or you are experiencing difficulties in the OVHcloud Control Panel?
    Create a support request in our Help Centre.
  • You require professional assistance for your project or you need help with tasks outside our support scope?
    Visit our partner portal to search for experts who are familiar with OVHcloud solutions.
  • You are looking for more detailed information regarding our support levels and Professional Services?
    Please visit our web pages for OVHcloud support levels and OVHcloud Professional Services.

You can participate in improving our documentation:

  • You would like to share feedback to improve a guide page or you want to report insufficient information on a specific page?
    Use the "Was this page helpful?" buttons at the bottom of the page to let us know.
  • You would like to propose a specific documentation update?
    Use the "Edit this page" function, available at the bottom of the page and in the sidebar.

Join our community of users.

Was this page helpful?