AI connections (myALCO MCP)

myALCO MCP connects a compatible AI assistant to your myALCO account. You can ask it to work on your website, read your support tickets, create a support request or add a reply to a ticket. MCP is the connection standard that lets the AI use these tools; your myALCO permissions still control what it can access.

Open the connections, integrations or MCP settings in your AI app and add a remote MCP server named myALCO MCP with the server URL https://alcohq.com/mcp. Start the connection, sign in on the myALCO page that opens, check the app and callback address, accept the notice and choose Connect AI app. Then ask the AI which account it is connected to, and to change nothing.

Any AI app that supports remote MCP connections with browser sign-in: remote Streamable HTTP, OAuth sign-in with PKCE and dynamic client registration. Availability depends on your AI provider, plan and organization settings. A desktop-only local MCP setup is a different connection type.

No. Never paste your myALCO password, session cookies, hosting credentials or SSH keys into an AI conversation. You sign in on the myALCO browser page, and supported apps do not need a client secret.

Check which myALCO account is connected; list and read tickets you can access, create a support request and add a client reply; and, for supported websites, list, read, create and update files, create folders and make file backups. Deleting, moving or restoring a file and running PHP maintenance each need your approval in myALCO.

It cannot reach another company's tickets or websites, read staff-only ticket notes or give itself more permissions. There is no server administrator, root, WHM or general shell tool, and not every myALCO feature has an MCP tool.

Yes. File edits can go live immediately, and not every edit has a separate approval screen. Ask the AI to inspect the current files and explain its plan first, review it before telling it to proceed, and check the live page, links, forms and phone layout afterwards.

The AI gives you an approval link. Open it, sign in if needed and check the address is on https://alcohq.com. Review the website, action, file paths and any code or arguments, tick the acknowledgement only if it matches your request, then tell the AI to run it. Approval alone does not run the change.

Approval is single-use and expires after five minutes. A changed action needs a new approval. If you decline or close the page, nothing is approved, and the AI cannot approve an action for you.

File updates keep a backup of the previous file, and you can ask the AI to back up a file first. Restoring a file needs its own approval. These are file restore points, not a full website or database backup: they do not reverse changes to customer records, orders or settings stored in a database.

Your prompts and tool results may be sent to your AI provider under its terms. Website access can be broad and may include website customer and subscriber records and payment-related website settings, so only connect a provider you are comfortable letting process that information.

Yes. It can read the tickets you are allowed to see, create a request for your company and post a client reply. Replies use the normal ticket system and may send its usual notifications. A submitted request does not mean ALCO has already done the work, so check the ticket for updates.

Open AI connections in myALCO (mcp-connect.php), find the app under Your connections and choose Revoke connection. Remove it from your AI app's settings too. Revoking stops future calls; it does not undo earlier changes or remove information already sent to the AI provider.

Connections expire after 30 days, or when the connected myALCO session ends. Reconnect from your AI app when it asks. Changes to your myALCO permissions apply the next time the AI tries an action.

File tools handle files up to 2 MB and do not follow links or show hidden dotfiles. PHP maintenance has short run-time and output limits, so larger jobs need to be split. Ask ALCO if a task cannot be done with the available tools.

That is expected. https://alcohq.com/mcp is a protocol endpoint for your AI app, not a web page. Add it in the AI app's MCP settings, and use AI connections in myALCO for the browser page.

Ask the AI which account is connected and confirm you used the right myALCO login. Website tools need website or hosting access on your account and a website ALCO has set up for MCP; contact ALCO to check.

Use the complete, fresh link the AI gave you. The page needs the request details in that link, and expired or used links show nothing. Ask the AI for a new link.

Stop further changes. Ask the AI what changed and which restore points exist, then contact ALCO. Include the AI app, the website, the time, the exact error and what you were trying to do, and leave out passwords, tokens, customer information and private approval links.