How do I connect Claude, ChatGPT or Cursor to my Hodi account?

You can connect your AI assistant to your Hodi services. It can then act for you: create a database, put your site online with Hodifly, read the logs when a site shows an error, change the PHP version, manage your DNS records, redirects and domain name servers, create mailboxes, add a subdomain or a cron job, run your Odoo instances managed with Hodiploy, and look up your invoices.

The connection goes through an MCP server, the standard that Claude, ChatGPT, Cursor and most assistants use. You give the assistant no password: you sign in with your Hodi login, and you decide what it may do.

In Claude: one click from the connectors directory

Open Hodi in the Claude directory and click Connect. It works for claude.ai and for the desktop and mobile apps, with nothing to copy.

The same goes for Claude Code: signed in with your Claude account, it already has Hodi as soon as you have connected it in Claude. Type /mcp to check: Hodi is in the list.

In other assistants: the address to add

https://hodi.host/mcp

For Cursor, you can also add it to mcp.json:

{
  "mcpServers": {
    "hodi": { "url": "https://hodi.host/mcp" }
  }
}

Allow access

The first time, your assistant opens a Hodi page:

1. Sign in with your Hodi login, as in your client area (two-factor authentication included).
2. Choose what the assistant may do: view only, or view and change (ticked by default, untick it for read-only access).
3. Click Allow. You are back in your assistant, connected.

The assistant reaches every client account linked to your user, including accounts added later, each within the permissions you have on it. If the account owner has limited you to some services or domains, the assistant only sees those. If you manage several, tell it which site or account you mean.

What the assistant can do

Read:

• list your hosting services, the domains configured on them, your MySQL and PostgreSQL databases, mailboxes and email forwarders;
• list the domain names registered at Hodi in your accounts, with their status, expiry date and auto-renewal, and read their name servers;
• read the DNS zone of a domain registered at Hodi or hosted with us, and its redirects;
• read a site's error logs, PHP settings, SSL certificates, disk space used;
• follow your Hodifly projects, their deployments and their build logs;
• list your Odoo instances managed with Hodiploy, with their status, metrics (CPU, memory, disk), logs and backups;
• list your invoices and show what each one covers, its balance and its status;
• search this help center for an answer.

With change access, also:

• create a MySQL or PostgreSQL database, with its user;
• create a Hodifly project from GitHub or, for a small project without GitHub, with a Git repository hosted by Hodifly that the assistant pushes the code to itself (when its environment cannot reach git.hodifly.app, it sends the code through the connector); deploy, roll back to an earlier version, manage environment variables;
• change the PHP version or a setting such as memory_limit;
• add a domain you already own to your hosting (as a separate site or an alias of the main one; nothing is registered or bought), a subdomain or a cron job;
• change your DNS records: for example connect your domain to Google Workspace, Microsoft 365 or Shopify (the assistant writes the records the provider asks for, all in one go);
• change the name servers of a domain registered at Hodi, for example to move its DNS to Cloudflare, or back to Hodi's;
• redirect a domain or subdomain to another address (permanent, temporary or masked);
• create a mailbox, reset its password, change its quota, add a forwarder, give you the settings for your mail app;
• request the free SSL certificates once a domain points to Hodi;
• for Odoo: start a backup, stop or start an instance, relaunch a deployment that failed, create a new instance (Community or Enterprise, with your own modules from GitHub), copy production into a staging instance to test an update, or give you a new master password for the database manager;
• open a ticket with technical support, with a summary of what was already tried.

The assistant cannot order, renew or pay, and it cannot delete an account, a database, a mailbox or an Odoo instance. The only things it removes are the DNS records and environment variables you ask it to change (the old mail records when you move to Google Workspace, for example). Each of its actions is written to your account's activity log.

If your domain's mail goes elsewhere (Google Workspace, Microsoft 365...), the assistant warns you when you create a mailbox on the hosting: it would receive nothing.

Before changing name servers, make sure the new DNS provider already has your records (website, mail): from that moment, the DNS zone at Hodi no longer applies. The change reaches the registry within minutes, and can take up to 48 hours to be seen everywhere.

Putting a site online without GitHub

If you already have a GitHub account, or your code is already there, that is the way: the assistant deploys from your repository. Otherwise, for a small project, it can create a Hodifly project "without GitHub": Hodifly hosts the Git repository, the assistant pushes the code to it, and every later push redeploys.

If the assistant works in an online environment whose network cannot reach git.hodifly.app (Claude Code on the web, for example), it sends the code through the connector itself, in parts: that suits a small site, not a big project. For a medium project, allow the domain git.hodifly.app in that environment's network settings (Claude Code on the web: environment settings, Network access, Custom) and its pushes go over git. For a bigger or long-lived project, GitHub stays the right answer.

This is not available in ChatGPT, which deploys from GitHub only.

Odoo instances with Hodiploy

The assistant works on the Hodiploy services of your accounts, with the same rules as the Hodiploy console: a production instance can only be changed by an administrator of the account, and a locked instance is never restarted.

A staging copy is a new instance made from production. Its scheduled jobs are switched off and its outgoing mail is caught, so testing never sends an e-mail to your customers. Its data is anonymised unless you ask otherwise.

To deploy your own modules, the assistant uses the GitHub repositories your Hodiploy account can reach. If GitHub is not connected yet, it gives you a one-time link that opens Hodiploy straight on the GitHub connection.

The assistant never chooses a master password. Hodiploy draws it, applies it (Odoo restarts for a few seconds), and the assistant hands it to you through a one-time link.

Your passwords stay out of the conversation

When the assistant creates a database, a mailbox, an API token or an Odoo master password, it does not give you the password in the conversation. It gives you a hodi.host/secret link, the same page you can use to send a password to someone: open it and click Reveal secret. The link works only once, within 24 hours, for whoever opens it first.

The link contains the password alone, with no address, user name or server: the assistant tells you in the conversation what it is for. A link that ends up in the wrong hands therefore says nothing about where the password opens. You can keep the password, or forward the link to the person who needs it (a developer, for example) without opening it yourself.

For an app deployed with Hodifly it is even simpler: ask the assistant to create the database "for my project", and it puts the connection details straight into the project's environment variables. The password appears nowhere.

In ChatGPT, this is the only way: a database is always created for a Hodifly project, and the assistant does not create API tokens, mailboxes or master passwords.

The values of your environment variables are never shown to the assistant, and the logs it reads are masked.

A few example requests

• "Put my repository my-org/my-site online at blog.example.com, with a PostgreSQL database."
• "Put this folder online at demo.example.com, without GitHub."
• "My site example.com shows a 500 error: look at the logs and tell me what is wrong."
• "Switch example.com to PHP 8.3 and raise memory_limit to 512M."
• "The last deployment of my project broke the site: roll back to the previous version."
• "Add a cron job that runs php artisan schedule:run every minute."
• "Connect example.com to Google Workspace, here is the verification code."
• "Redirect example.fr to https://www.example.com."
• "Create the mailbox contact@example.com."
• "Which of my domains expire in the next three months?"
• "Point example.com to Cloudflare's name servers: ada.ns.cloudflare.com and bob.ns.cloudflare.com."
• "Make a staging copy of my Odoo production so I can test the update."
• "Why is my Odoo instance slow? Look at its memory over the last 24 hours."
• "Do I have any unpaid invoices?"

Your assistant also offers ready-made requests, such as "Deploy a Laravel app" or "My site shows an error".

Remove access

In your client area, open your account menu, then AI assistants. You see each connected app, its access level and when it was last used. Remove access cuts the connection immediately. In Claude, you can also disconnect Hodi under Settings > Connectors.

If you are not the account owner

A user added to a client account by its owner only has the permissions they were given. To act on a hosting service or a Hodiploy service, the assistant needs the same permissions you have in the client area (manage products, single sign-on, tickets); to see registered domains, change their DNS or their name servers, the permission to manage domains; to see invoices, the permission to view invoices. If the owner has limited your access to some services or domains, the assistant reaches only those. The owner can change all this in User Management.

If something does not work

To learn more about the data kept, read our privacy policy.

Updated on: 07/11/2026