Connect Claude and ChatGPT to TurboStack

Connect Claude, ChatGPT or another AI assistant to your TurboStack account. Ask about your hosts, Health, Threat Center and Monitoring, and deploy a host.

The TurboStack MCP server connects an artificial intelligence (AI) assistant, such as Claude or ChatGPT, to your TurboStack account. You can then ask the assistant about your hosts in plain language, and it answers from your live TurboStack data.

It uses the Model Context Protocol (MCP), the open standard that AI assistants use to connect to external tools and data. The server address (Uniform Resource Locator, or URL) is:

https://my.turbostack.app/mcp

What you can do with it

  • Get an overview of your hosts and the issues that need attention.
  • Read Health: the problems TurboStack's analysis found, and the reports that explain them.
  • Read the Threat Center: vulnerabilities, Indicators of Compromise (IoC) and runtime detections.
  • Read Monitoring: the monitored services of a host, and metrics such as load, memory and disk.
  • Read a host's configuration and the status of its latest deploy.
  • Deploy a host: publish its saved configuration, the same as Save & Publish in TurboStack.

The assistant cannot change a configuration, dismiss a finding or run a full deploy. Those stay in the TurboStack Platform.

Requirements

  • A TurboStack login that can sign in at https://my.turbostack.app. If you use two-factor authentication, you need your authenticator app.

  • An AI assistant that supports remote MCP servers with sign-in. Claude and ChatGPT do. Some plans or workspaces need an administrator to allow custom connectors first.

Connect your AI assistant

In each case you add the server, and then sign in with your TurboStack login. See Sign in and permissions for what happens during sign-in.

Claude (web, Desktop and mobile)

  1. In Claude, open Settings > Connectors.

  2. If TurboStack is listed under Browse connectors, select it and click Connect.

  3. If it is not listed, click Add custom connector. Enter the name TurboStack and the URL https://my.turbostack.app/mcp, then click Add and Connect.

  4. Sign in to TurboStack and click Allow.

A connector that you add on the web or in Claude Desktop is also available in the Claude mobile apps. On a Team or Enterprise plan, an owner may have to add or allow the connector for the organization first.

Claude Code

Add the server from your terminal:

claude mcp add --transport http turbostack https://my.turbostack.app/mcp

Then start Claude Code, run /mcp, select turbostack and choose to authenticate. Your browser opens the TurboStack sign-in.

ChatGPT

  1. In ChatGPT, open Settings > Apps and Connectors.

  2. If TurboStack is listed in the directory, select it and click Connect.

  3. If it is not listed, turn on Developer mode under the advanced settings. Then create a custom app or connector with the URL https://my.turbostack.app/mcp and OAuth as the authentication.

  4. Sign in to TurboStack and click Allow.

Developer mode is not available on every ChatGPT plan, and OpenAI changes these menu names from time to time. Check the OpenAI help pages if a step looks different.

Other MCP clients

Give the client the URL https://my.turbostack.app/mcp. The server uses Streamable HTTP and OAuth 2.1 sign-in with Proof Key for Code Exchange (PKCE). The client registers itself automatically, so you do not need a client ID or secret.

After sign-in, the browser has to return to Claude, ChatGPT or to a local address on your own computer (localhost or 127.0.0.1). A client that returns to another address is refused at sign-in.

You also find the server URL in TurboStack itself: open the profile menu (top right) and choose MCP. That page has a Copy button and links to the Claude and ChatGPT settings.

Sign in and permissions

When you connect, your AI assistant opens a TurboStack page in your browser.

  1. Sign in with your normal TurboStack email address and password. If two-factor authentication is on, enter the code from your authenticator app. If you are already signed in to TurboStack in that browser, this step is skipped.

  2. Check the consent screen. It names the app that wants access, for example Claude. Under Logged in as it shows the login the app will act for, and Access to your own hosts only.

  3. Click Allow to connect, or Deny to cancel.

The assistant then works as your TurboStack login, with the same access. It sees only the hosts that this login can see in TurboStack:

  • A login for the whole account sees all hosts of that account.
  • A contact that has access to only some services sees just those hosts.
  • If your login has access to more than one account, the connection uses the account that is open in TurboStack when you click Allow. To connect another account, sign in to TurboStack in the same browser, select that account, and connect again.

Hosts that are not active, and hosts that are members of a cluster, are not available through the MCP server.

What the assistant can see and do

The assistant uses these tools. It picks them itself, based on your question. You do not need to name them.

Tool What it does Changes anything?
current_user Shows which TurboStack login the connection acts for. No
list_hosts Lists the hosts you can see, with their ID, name and type. It can filter by part of a name. No
get_host Shows one host and its TurboStack configuration, the same settings you see in the Source (YAML) view. No
get_health_issues Shows the problems that TurboStack's analysis found, as on the Health page. For one host or for all your hosts. No
get_health_reports Shows the Health reports that explain an issue and recommend a fix. No
get_threats Shows Threat Center findings: vulnerabilities (optionally by priority), Indicators of Compromise or runtime detections. No
get_monitoring Shows the Monitoring services of a host and its metrics, such as load, memory and disk. Without a host, it lists the monitored services of all your hosts. No
get_deploy_status Shows the latest deploy of a host: whether it is still running, how it ended, who started it and when, and the end of its output. No
deploy_host Deploys a host: it publishes the saved configuration to the live server. Yes

All tools except deploy_host only read data.

Deploy safely

deploy_host is the only tool that changes anything. It does exactly what Save & Publish does in TurboStack: a normal deploy of the configuration that is saved for the host. See Publishing changes.

These safeguards apply:

  • Your AI assistant asks you first. The tool is marked as one that changes data. Claude and ChatGPT therefore ask you to approve each call before it runs. Read the host name in that request before you approve.

  • The exact host name is required. The assistant has to send the exact name of the host with the request. A deploy with a wrong or guessed host is refused.

  • Never a full deploy. Save & Full Publish and Save, Delete & Full Publish are not available through the MCP server. Use the TurboStack Platform for those.

  • One deploy at a time. A host that is already deploying is refused.

  • It is logged under your name. The deploy appears with your email address on the Deploys tab of the host's History, like a publish from TurboStack.

After a deploy, ask the assistant to check the deploy status, or follow it in TurboStack.

Example prompts

Replace web1.example.com with the name of one of your hosts.

  • "Which of my hosts have open Health issues? Start with the most severe."

  • "Show the Threat Center findings for web1.example.com. Which critical vulnerabilities should I fix first?"

  • "Are there any Indicators of Compromise or runtime detections on my hosts?"

  • "Is the disk on web1.example.com filling up? Also check memory and load."

  • "Did the last deploy of web1.example.com succeed, and who started it?"

  • "Which PHP version do the applications on web1.example.com use?"

  • "Deploy web1.example.com." The assistant asks you to confirm before it starts, then reports the deploy status.

Privacy and data

  • The assistant sees only what your login can see. It has no access to other accounts or to hosts outside your permissions.

  • Data goes to your AI provider. Everything a tool returns is sent to the AI provider you use, for example Anthropic or OpenAI. That includes host names, configuration, and Health and Threat Center findings. The provider processes this data under its own terms and privacy policy.

  • Configuration can contain secrets. A host's configuration can hold values you entered yourself, such as the private key of a custom certificate or a Cloudflare API token. When the assistant reads that host's configuration, those values are sent to the AI provider too.

  • Your login and password stay with TurboStack. You sign in on the TurboStack page. The AI assistant never receives your password or your two-factor code.

Hosted Power processes your data as described in its privacy policy and its terms of service.

Disconnect

Disconnect TurboStack in your AI assistant:

  • Claude: open Settings > Connectors, select TurboStack, and choose Disconnect or remove the connector.

  • ChatGPT: open Settings > Apps and Connectors, select TurboStack, and disconnect or delete it.

  • Claude Code: run claude mcp remove turbostack.

TurboStack itself does not have a page yet where you can see or remove connected AI assistants. If you need access removed on the TurboStack side, for example after a lost device or when a colleague leaves, contact Support.

Troubleshooting

Problem What to do
Sign-in keeps returning to the TurboStack login page Sign in to https://my.turbostack.app in the same browser first, then connect again. Allow cookies for my.turbostack.app, and check that your login works in TurboStack itself.
TurboStack says "You don't have access to GUI TurboStack" Your contact does not have the TurboStack permission yet. See Accounts and access.
Sign-in fails with a redirect or registration error Your client returns to an address that TurboStack does not accept. Use Claude, ChatGPT or Claude Code, or a client that returns to localhost.
"Host ... was not found, or this account may not see it" The host is outside your access: it belongs to another account, your contact has no access to it, it is a cluster member, or it is not active. Ask the assistant to run list_hosts to see the hosts you can use.
You see too few hosts You may be connected to a different account. Ask the assistant which login it uses (current_user). See Sign in and permissions.
"confirm_host_name must be exactly the host name" The assistant sent a host name that does not match. Give it the exact name from TurboStack and ask again.
"... is already deploying" A deploy of that host is still running. Wait for it to finish, and check it with the deploy status or in the host's History.
The deploy started but ended with an error Open the host in TurboStack and read the deploy output on the Deploys tab. See Publishing changes.
"Monitoring is not available right now" Monitoring data could not be loaded. Try again later, or open the host's Health tab.
The tools do not appear Disconnect and connect again, and check that you clicked Allow. On a Team or Enterprise plan, ask your administrator whether custom connectors are allowed.

Support

For help with the TurboStack MCP server, email support@hosted-power.com or see Support for the other ways to reach us.

© 2026 Hosted Power — TurboStack