MCP (Model Context Protocol) is the standard AI apps use to connect to outside services. HostUp runs a native MCP server \u2014 a first among hosting providers in Sweden.<\/p>\n\n\n\n
The server is hosted by us. You add one address in your AI app and your services are there. There is nothing to install on your machine.<\/p>\n\n\n\n
<\/span>Before you start<\/span><\/h2>\n\n\n\nYou need two things: a HostUp account with at least one service, and an AI app that supports MCP connectors. Claude works on every plan including the free one. ChatGPT needs Plus or Pro, because connectors sit behind developer mode.<\/p>\n\n\n\n
<\/span>Step 1: Create an API key<\/span><\/h2>\n\n\n\nThe key is what ties your AI app to your account. Go to API Management<\/a> in the client area and click Create API Key<\/strong>.<\/p>\n\n\n\nGive it a name you’ll recognise \u2014 “Claude”, say \u2014 then open the Permissions<\/strong> tab. This is where you decide what your AI is allowed to do.<\/p>\n\n\n\n![\"The](\"https:\/\/hostup.se\/en\/support\/wp-content\/uploads\/2026\/07\/en-06-permissions.png\")
The scopes you tick decide exactly which tools your AI can see.<\/figcaption><\/figure>\n\n\n\n<\/span>Which permissions should I pick?<\/span><\/h3>\n\n\n\nPermissions aren’t only a lock \u2014 they decide what your AI can even see. Leave out the write scopes and the tools that change things never appear. Your AI can look your services up but not touch them, and it won’t suggest changes it can’t make anyway.<\/p>\n\n\n\n
\n- Just want to ask questions?<\/strong> Leave
read:all<\/code> ticked and skip the write scopes. You get a connector that can answer anything about your services but never change one.<\/li>\n- Want it to handle one job?<\/strong> Go narrow. A key with only
read:dns<\/code> and write:dns<\/code> gives you an AI that helps with DNS records and nothing else.<\/li>\n- Want it to handle everything?<\/strong> Tick
read:all<\/code> and write:all<\/code>.<\/li>\n<\/ul>\n\n\n\nOne thing to weigh: the full toolset takes up roughly 20,000 tokens of your AI’s memory every time it uses the connector. Give it the scopes you actually plan to use and you leave more room for the conversation itself.<\/p>\n\n\n\n
You can change your mind later. If your AI runs into a missing tool, it also gets a link that upgrades that same key \u2014 no need to create a new one and reconnect.<\/p>\n\n\n\n
<\/span>Step 2: Add the connector in your AI app<\/span><\/h2>\n\n\n\nFurther down the same page you’ll find the AI connectors (MCP)<\/strong> card. It has ready-made instructions for each app \u2014 pick your tab and copy what’s there.<\/p>\n\n\n\n![\"The](\"https:\/\/hostup.se\/en\/support\/wp-content\/uploads\/2026\/07\/en-01-mcp-card.png\")
The AI connectors (MCP) card on the API Management page.<\/figcaption><\/figure>\n\n\n\n<\/span>Claude<\/span><\/h3>\n\n\n\nGo to Settings \u2192 Connectors \u2192 Add custom connector<\/strong> in the Claude app or on claude.ai. Paste the address below with your API key filled in, and leave authentication set to “None”.<\/p>\n\n\n\nhttps:\/\/cloud.hostup.se\/mcp\/k\/<your API key><\/code><\/pre>\n\n\n\n![\"The](\"https:\/\/hostup.se\/en\/support\/wp-content\/uploads\/2026\/07\/en-02-claude-tab.png\")
<\/figure>\n\n\n\n<\/span>ChatGPT<\/span><\/h3>\n\n\n\nGo to Settings \u2192 Apps & Connectors<\/strong>, turn on Developer mode<\/strong> and create a new connector. Use the same address as for Claude and set authentication to “None”.<\/p>\n\n\n\n![\"The](\"https:\/\/hostup.se\/en\/support\/wp-content\/uploads\/2026\/07\/en-03-chatgpt-tab.png\")
<\/figure>\n\n\n\n<\/span>Claude Code<\/span><\/h3>\n\n\n\nRun this in your terminal with your key filled in:<\/p>\n\n\n\n
claude mcp add --transport http hostup \\\n https:\/\/cloud.hostup.se\/mcp \\\n --header \"Authorization: Bearer <your API key>\"<\/code><\/pre>\n\n\n\nHere the key sits in a header rather than in the address, which is safer. The same setup works in Cursor and VS Code.<\/p>\n\n\n\n![\"The](\"https:\/\/hostup.se\/en\/support\/wp-content\/uploads\/2026\/07\/en-04-claude-code-tab.png\")
<\/figure>\n\n\n\n<\/span>Cursor and other MCP clients<\/span><\/h3>\n\n\n\nAdd a remote MCP server (Streamable HTTP) with the address https:\/\/cloud.hostup.se\/mcp<\/code> and send your key as a header:<\/p>\n\n\n\nAuthorization: Bearer <your API key><\/code><\/pre>\n\n\n\n![\"The](\"https:\/\/hostup.se\/en\/support\/wp-content\/uploads\/2026\/07\/en-05-cursor-tab.png\")
<\/figure>\n\n\n\n<\/span>What happens when your AI changes something?<\/span><\/h2>\n\n\n\nWhat you ask for happens right away, exactly as if you had made the API call yourself. Your AI app checks with you first every time \u2014 that’s the app’s own approval prompt before it uses a tool.<\/p>\n\n\n\n
Two kinds of action make an extra stop at our end and finish with a confirmation link you open in your browser:<\/p>\n\n\n\n
\n- Anything that costs money.<\/strong> Registering a domain, ordering a service, paying an invoice.<\/li>\n
- Anything you can’t undo.<\/strong> Reinstalling a VPS, restoring from a backup, and cancelling a service.<\/li>\n<\/ul>\n\n\n\n
In those cases your AI prepares the action and shows you a summary plus a link. Nothing goes through until you click. So your AI can never buy something on your behalf or wipe a server on its own.<\/p>\n\n\n\n
Other changes \u2014 adding a DNS record, switching PHP version, creating an email address \u2014 happen directly. If you want a connector that can’t change anything at all, the key’s permissions are the tool for that, not the confirmation links.<\/p>\n\n\n\n
Every action is logged to your account and shows up in the audit log<\/a>.<\/p>\n\n\n\n<\/span>Security: treat the address like a password<\/span><\/h2>\n\n\n\nIf you use the variant with the key in the address \u2014 the one Claude and ChatGPT use \u2014 then the address itself contains your API key. Anyone who has it can act on your account within that key’s permissions.<\/p>\n\n\n\n
\n- Never share the address, and don’t paste it into shared documents or chats.<\/li>\n
- Use the header variant where your app supports it \u2014 that keeps the key out of the address.<\/li>\n
- Think a key has leaked? Revoke it under API Management<\/a> and create a new one. The old one stops working immediately.<\/li>\n<\/ul>\n\n\n\n
Bear in mind too that the conversation in your AI app can hold sensitive material. Ask for an EPP code or a cPanel login link and it lands in your chat history \u2014 treat that history accordingly.<\/p>\n\n\n\n
<\/span>If something doesn’t work<\/span><\/h2>\n\n\n\n<\/span>Your AI says it can’t do something<\/span><\/h3>\n\n\n\nAlmost always the key is missing a permission. Your AI gets a link that upgrades that same key \u2014 click it, then start a new conversation if the new tools don’t show up straight away.<\/p>\n\n\n\n
<\/span>The connector doesn’t respond<\/span><\/h3>\n\n\n\nCheck that the key was copied correctly and hasn’t been revoked. Each key is allowed 300 requests per five-minute window, so heavy use may mean waiting a moment.<\/p>\n\n\n\n
<\/span>A slow diagnostic times out in Claude Code<\/span><\/h3>\n\n\n\nClaude Code waits 30 seconds for a tool by default. Some diagnostics take longer. Raise the limit with:<\/p>\n\n\n\n
MCP_TOOL_TIMEOUT=120000<\/code><\/pre>\n\n\n\n<\/span>Prefer our own assistant?<\/span><\/h2>\n\n\n\nThe built-in assistant in the client area does the same things and needs no key. The difference is that an MCP connector lets you work in the app you already have open, with its newest model. Both exist \u2014 pick whichever suits you.<\/p>\n\n\n\n
There’s a more technical walkthrough at developer.hostup.se<\/a>.<\/p>\n\n\r\n\t\t\t\r\n\r\n\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\tWas this article helpful?<\/h3>\r\n\t\t\t\t\t<\/div>\r\n\t\t\t\t\t
The key is what ties your AI app to your account. Go to API Management<\/a> in the client area and click Create API Key<\/strong>.<\/p>\n\n\n\n Give it a name you’ll recognise \u2014 “Claude”, say \u2014 then open the Permissions<\/strong> tab. This is where you decide what your AI is allowed to do.<\/p>\n\n\n\n Permissions aren’t only a lock \u2014 they decide what your AI can even see. Leave out the write scopes and the tools that change things never appear. Your AI can look your services up but not touch them, and it won’t suggest changes it can’t make anyway.<\/p>\n\n\n\n One thing to weigh: the full toolset takes up roughly 20,000 tokens of your AI’s memory every time it uses the connector. Give it the scopes you actually plan to use and you leave more room for the conversation itself.<\/p>\n\n\n\n You can change your mind later. If your AI runs into a missing tool, it also gets a link that upgrades that same key \u2014 no need to create a new one and reconnect.<\/p>\n\n\n\n Further down the same page you’ll find the AI connectors (MCP)<\/strong> card. It has ready-made instructions for each app \u2014 pick your tab and copy what’s there.<\/p>\n\n\n\n Go to Settings \u2192 Connectors \u2192 Add custom connector<\/strong> in the Claude app or on claude.ai. Paste the address below with your API key filled in, and leave authentication set to “None”.<\/p>\n\n\n\n Go to Settings \u2192 Apps & Connectors<\/strong>, turn on Developer mode<\/strong> and create a new connector. Use the same address as for Claude and set authentication to “None”.<\/p>\n\n\n\n Run this in your terminal with your key filled in:<\/p>\n\n\n\n Here the key sits in a header rather than in the address, which is safer. The same setup works in Cursor and VS Code.<\/p>\n\n\n\n Add a remote MCP server (Streamable HTTP) with the address What you ask for happens right away, exactly as if you had made the API call yourself. Your AI app checks with you first every time \u2014 that’s the app’s own approval prompt before it uses a tool.<\/p>\n\n\n\n Two kinds of action make an extra stop at our end and finish with a confirmation link you open in your browser:<\/p>\n\n\n\n In those cases your AI prepares the action and shows you a summary plus a link. Nothing goes through until you click. So your AI can never buy something on your behalf or wipe a server on its own.<\/p>\n\n\n\n Other changes \u2014 adding a DNS record, switching PHP version, creating an email address \u2014 happen directly. If you want a connector that can’t change anything at all, the key’s permissions are the tool for that, not the confirmation links.<\/p>\n\n\n\n Every action is logged to your account and shows up in the audit log<\/a>.<\/p>\n\n\n\n If you use the variant with the key in the address \u2014 the one Claude and ChatGPT use \u2014 then the address itself contains your API key. Anyone who has it can act on your account within that key’s permissions.<\/p>\n\n\n\n Bear in mind too that the conversation in your AI app can hold sensitive material. Ask for an EPP code or a cPanel login link and it lands in your chat history \u2014 treat that history accordingly.<\/p>\n\n\n\n Almost always the key is missing a permission. Your AI gets a link that upgrades that same key \u2014 click it, then start a new conversation if the new tools don’t show up straight away.<\/p>\n\n\n\n Check that the key was copied correctly and hasn’t been revoked. Each key is allowed 300 requests per five-minute window, so heavy use may mean waiting a moment.<\/p>\n\n\n\n Claude Code waits 30 seconds for a tool by default. Some diagnostics take longer. Raise the limit with:<\/p>\n\n\n\n The built-in assistant in the client area does the same things and needs no key. The difference is that an MCP connector lets you work in the app you already have open, with its newest model. Both exist \u2014 pick whichever suits you.<\/p>\n\n\n\n There’s a more technical walkthrough at developer.hostup.se<\/a>.<\/p>\n\n\r\n\t\t\t<\/span>Which permissions should I pick?<\/span><\/h3>\n\n\n\n
\n
read:all<\/code> ticked and skip the write scopes. You get a connector that can answer anything about your services but never change one.<\/li>\nread:dns<\/code> and write:dns<\/code> gives you an AI that helps with DNS records and nothing else.<\/li>\nread:all<\/code> and write:all<\/code>.<\/li>\n<\/ul>\n\n\n\n<\/span>Step 2: Add the connector in your AI app<\/span><\/h2>\n\n\n\n
<\/span>Claude<\/span><\/h3>\n\n\n\n
https:\/\/cloud.hostup.se\/mcp\/k\/<your API key><\/code><\/pre>\n\n\n\n<\/figure>\n\n\n\n<\/span>ChatGPT<\/span><\/h3>\n\n\n\n
<\/figure>\n\n\n\n<\/span>Claude Code<\/span><\/h3>\n\n\n\n
claude mcp add --transport http hostup \\\n https:\/\/cloud.hostup.se\/mcp \\\n --header \"Authorization: Bearer <your API key>\"<\/code><\/pre>\n\n\n\n<\/figure>\n\n\n\n<\/span>Cursor and other MCP clients<\/span><\/h3>\n\n\n\n
https:\/\/cloud.hostup.se\/mcp<\/code> and send your key as a header:<\/p>\n\n\n\nAuthorization: Bearer <your API key><\/code><\/pre>\n\n\n\n<\/figure>\n\n\n\n<\/span>What happens when your AI changes something?<\/span><\/h2>\n\n\n\n
\n
<\/span>Security: treat the address like a password<\/span><\/h2>\n\n\n\n
\n
<\/span>If something doesn’t work<\/span><\/h2>\n\n\n\n
<\/span>Your AI says it can’t do something<\/span><\/h3>\n\n\n\n
<\/span>The connector doesn’t respond<\/span><\/h3>\n\n\n\n
<\/span>A slow diagnostic times out in Claude Code<\/span><\/h3>\n\n\n\n
MCP_TOOL_TIMEOUT=120000<\/code><\/pre>\n\n\n\n<\/span>Prefer our own assistant?<\/span><\/h2>\n\n\n\n
Was this article helpful?<\/h3>\r\n\t\t\t\t\t<\/div>\r\n\t\t\t\t\t