> ## Documentation Index
> Fetch the complete documentation index at: https://kb.hosting.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Connecting Claude and other AI assistants to your account
> How to connect Claude, ChatGPT or another MCP client to your hosting.com account, what it can then do, and how to review or revoke that access.
hosting.com runs an MCP server, so an AI assistant such as Claude or ChatGPT can work with your account directly. Once connected, you can ask it to check what is due, look up a domain's nameservers, read a PHP error log, or create a mailbox, and it will make the calls itself.
**A connected assistant can spend money and delete things.** It has the same reach over your account that you do, which includes **paying an invoice**, **deleting a website**, **deleting a database or a mailbox**, and **changing nameservers**, which can take a site offline.
Connect it to accounts you are comfortable with it changing, read what it proposes before you approve it, and disconnect it when you are done. See [reviewing and revoking access](#reviewing-and-revoking-access) below.
## What you need
* A hosting.com account, and your normal login for it
* An AI assistant that supports MCP connectors, such as Claude or ChatGPT
* The server address: `https://api.hosting.com/mcp`
There is nothing to install, no API key to generate beforehand, and no setting to switch on in the Hosting Panel first.
## Connecting
The exact wording differs between assistants and changes fairly often, but the shape is the same everywhere.
1. In your assistant, find where custom connectors or MCP servers are added. In Claude this is under **Settings**, then **Connectors**.
2. Add a new custom connector and give it the server URL `https://api.hosting.com/mcp`.
3. Your browser opens a hosting.com sign-in page. Sign in as you normally would, including your second factor if you have one.
4. Review what the connection is asking for, and approve it.
5. You are returned to your assistant, and the connection is live.
**You are signing in at hosting.com, not handing your password to the assistant.** The sign-in happens in your own browser on our page, and the assistant receives only a token. It never sees your password, and the token can be revoked without changing it.
A good first thing to ask is something read-only, such as "what services do I have and when do they renew?" It confirms the connection works before anything is at stake.
## What it can do once connected
Everything in the API is available to the assistant as a tool. In practice that covers:
| Area | Examples of what you can ask for |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Billing** | What is outstanding, what an invoice is for, what credit you hold, and paying an invoice |
| **Domains** | What you own and when it expires, whether a name is available and what it costs, nameservers, registrar lock, glue records |
| **Websites** | Create or delete a site, install an application, get a WordPress login link, update WordPress core, change the PHP version, read the PHP error log, manage databases and users, issue an SSL certificate |
| **Email** | Create, suspend or delete a mailbox, send a password-reset link, manage forwarders and aliases, set the catch-all, turn on DKIM |
| **Support** | Read your tickets and their conversations. It cannot open or reply to one |
| **Your account** | Your profile, your services, renewal dates and prices |
### Two limits worth knowing
**It can only ever reach your own account.** The token is tied to the account you signed in as, and no call can touch another one.
**Deletions have to name what they are deleting.** Any call that removes something has to repeat the exact domain or address back, which means an assistant cannot delete the wrong mailbox through a mistyped parameter. It is a real guard rail, though it is not a substitute for reading what it proposes.
## Reviewing and revoking access
A connection stays live until you end it. There are two ways to do that.
**Disconnect it in the assistant.** Removing the connector at that end stops it being used.
**Revoke the session at our end.** Your account keeps a list of the sessions signed in to it, and any one of them can be revoked. This is the one to use if you no longer have the assistant to hand, or if you are not certain what is connected.
Revoke the session if a device with the assistant on it is lost or stolen, if you are handing a machine to someone else, or if you simply want to be sure nothing is still connected. Revoking does not affect your password or your other sign-ins.
## If something is not working
| What you see | What it usually means |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
| The assistant says it is **not authorised**, or you are asked to sign in again | The token has expired or been revoked. Reconnect the connector |
| It says it **does not have permission** for a particular action | The connection is missing the scope or consent for that call. Remove the connector and add it again, approving the access it asks for |
| It cannot find something you know exists | It is looking on the account you signed in as. If you have more than one account, check you connected the right one |
| It reports that **a change is already in progress** | Something else is already changing the same thing. Wait for that to finish and try again |
| Requests start failing after a burst of activity | You have hit a rate limit. Wait a little and continue |
## Related articles
* [The hosting.com API and MCP server](/docs/hosting-api-and-mcp)
* [Signing in to the API](/docs/signing-in-to-the-api)
* [Recovering account access](/docs/recovering-account-access)