Skip to content
Docs
hi-client.com (opens in a new tab)

AI agents in hiClient

Download

Connect Claude, Claude Code, ChatGPT or another MCP client to your hiClient account with OAuth 2.1 and permissions you choose.

You can connect an AI assistant to your hiClient account so it can read and do the same things you do in the portal: offers, bookings, forms, website, messages, tickets, publications, reports, devices and profile.

The connection uses two open standards:

  • MCP (Model Context Protocol): the assistant calls hiClient tools such as offers_list or site_publish.
  • OAuth 2.1: you sign in to hiClient and choose which permissions to grant. The assistant never sees your password.

Server address

https://mcp.hi-client.com/mcp

It is the only address you need. The assistant discovers on its own how to ask for authorization.

Supported assistants

Assistant Guide
Claude (web or desktop) Connect Claude
Claude Code Connect Claude Code
ChatGPT Connect ChatGPT
Another MCP client Any client with HTTP transport and OAuth 2.1 with PKCE.

How it works

  1. You add the server address in your assistant.
  2. The assistant opens hiClient in the browser. You sign in; if your account uses two-step verification, you may be asked for the code.
  3. You see which assistant is asking for access and with which permissions. You can remove permissions before authorizing.
  4. You authorize. From then on the assistant only sees the tools of the granted permissions.
  5. The connection stays active until you revoke it in Connected agents.

What an agent can do

With the permissions you grant, an agent can, for example:

  • List offers, create a new one or duplicate an existing one and publish it.
  • Review bookings and the month calendar.
  • Edit the site draft, add plugins, upload images and publish.
  • Read visitor messages, change their state, tag them and handle support tickets.
  • Check figures, sales and orders.
  • Rename devices and add alert recipients.
  • Update the public profile, language, theme and portal home.

The details are in Permissions and Tools.

What it can never do

No permission grants these operations. No agent can request them:

  • Change the plan, subscribe, pay or collect payments. Nor move money or configure payment methods.
  • Manage domains.
  • Touch account security: password, two-step verification, sessions, account e-mail.
  • Export or delete the account.
  • See people's data: names or contact details of those who book or buy, records, faces or biometrics. The hiClient server does not store records or biometrics, and bookings are returned without the identity of the person who booked.

An agent adds protections, never reduces them

Some actions exist in the portal but no permission grants them to an agent, because they would turn off a protection or erase evidence. If an agent tries one, it gets the portal_only error and you do it in the portal:

  • Pausing the alert e-mail channel.
  • Removing an alert recipient that is already verified.
  • Disabling or trimming the channels of the security-change notice.
  • Changing the biometric deletion option on unlink.
  • Deleting inbox messages (the agent can close the conversation).
  • Deleting the site.
  • Revoking a device or choosing which device keeps a seat: the portal asks for a recent sign-in, which an agent cannot give.

The opposite is allowed: an agent can resume alerts, add recipients or widen notices. When an agent activates a new alert recipient, you get a security-change notice that the agent cannot turn off.

Next steps