Connect an AI assistant to hosting with Hostbrid MCP

You can connect an MCP-compatible client to your Hostbrid account to inspect resources and, with additional permissions, request selected actions. A new key is read-only. Creating resources, preparing purchases and deleting them use separate permissions; a purchase is not charged until you confirm it in your panel.

This connection manages account resources. It does not deploy a Git repository by itself: connect the repository through Projects. If you want to build and host your own MCP server, see the separate guide to running an MCP server on a VPS.

If you are integrating a script without an MCP client, follow the guide to make your first REST API request.

1. Create an MCP key in Hostbrid

Sign in to the panel and open AI keys. Create a key and store it in a secrets manager. The full value is shown once; do not paste it into a chat, repository, screenshot or shared file.

A new key can only read. If you need to change resources, request the specific permissions in the panel; deletion is separate. Avoid granting every permission “just in case”.

2. Add the server to an MCP-compatible client

In the client’s remote-server settings, enter the endpoint and authorization header. Replace nxp_your_key with the real key inside the client’s secure settings:

{
  "mcpServers": {
    "hostbrid": {
      "type": "http",
      "url": "https://my.hostbrid.com/mcp",
      "headers": {
        "Authorization": "Bearer nxp_your_key"
      }
    }
  }
}

The endpoint uses remote MCP over HTTP with Bearer authentication. The exact setting depends on the client: confirm your version supports remote HTTP MCP servers and custom headers. Do not put the key in the URL; secrets in URLs can end up in browser history and logs.

3. Test the connection before allowing changes

Start with a harmless prompt such as: “List my sites and tell me which plan each uses; do not change anything.” Check that the response shows the expected account and resource scope. The read-only key can inspect sites, domains, databases and machine status according to the current tool catalogue.

If the client cannot connect, check for spaces in the token, the Bearer prefix and remote HTTP support. Create a replacement key if the old one may have been exposed, then revoke the unused key.

4. Grant only the permission the task needs

Tools are grouped by scope. Some lower-risk actions can be enabled for writing; preparing paid orders uses a separate permission. Deletion is separate too and shows what would be lost first. Read the current catalogue and examples on the Hostbrid MCP page before authorizing actions.

A purchase request prepares the configuration and price for review; your AI cannot confirm payment or access your card details. Open the panel, check the amount, billing period and extras, then confirm yourself if you want to proceed. For deletion, review the preview before allowing the action.

What it can and cannot do

• It can read data in the MCP catalogue and run actions covered by the permissions you grant.
• It does not reveal database, email, FTP or shell passwords.
• It does not replace your Git repository or the build and deployment settings in Projects.
• An AI response is not proof that your application works: test the site, backend and data after deployment.
• The REST API and MCP are separate interfaces. For software automation without an AI client, use the public API reference.

Frequently asked questions

Can I connect Claude, Cursor or another client?

Use a client that supports remote MCP servers over HTTP and authentication headers. Menus and requirements vary by client and version; check that application’s connection guide.

Does MCP deploy my website from GitHub?

No. The account MCP manages resources exposed by its tools. To import and deploy a repository, use Projects and verify the framework, build commands and output directory.

Can the AI buy or delete without me seeing it?

A purchase is prepared for you to confirm in the panel. Deletion requires its own permission and shows a preview of what will be lost. Keep permissions disabled when you do not need them.

See the current MCP catalogue, permissions and examples, the API and hosting documentation, and guides to publishing Git projects.