Connect GARMTECH MCP to ChatGPT, Claude, VS Code and other AI clients

GARMTECH MCP lets a compatible AI client work with websites, domains, DNS, files, logs, databases, FTP users and supported WordPress operations in your account.

Server address (the same for every client):

https://my.garmtech.com/mcp

You do not need an API key. On the first connection your browser opens My.GARMTECH: sign in, select the client account, review the requested access and approve it. Never paste your My.GARMTECH or Plesk password into an AI client.

Quick install

• Add to Claude
• Add to Replit
• VS Code – add the server with the .vscode/mcp.json example below.
• LM Studio and Goose – in the app's MCP settings add a remote server (Streamable HTTP) with the address above.

Cursor has its own install button on My.GARMTECH → Services → MCP Connections. After accepting an install link, start the server and complete the browser sign-in when the client asks for it.

Command-line clients

Claude Code:

claude mcp add --transport http garmtech https://my.garmtech.com/mcp

Codex CLI:

codex mcp add garmtech --url https://my.garmtech.com/mcp
codex mcp login garmtech

Gemini CLI:

gemini mcp add --transport http garmtech https://my.garmtech.com/mcp

After adding the server, open the client's MCP screen. If the browser does not open right away, the first protected request starts the OAuth sign-in.

Other supported clients

Configuration for VS Code (.vscode/mcp.json):

{
  "servers": {
    "garmtech": {
      "type": "http",
      "url": "https://my.garmtech.com/mcp"
    }
  }
}

Configuration for Cursor, Zed, Warp, Windsurf and similar clients:

{
  "mcpServers": {
    "garmtech": {
      "url": "https://my.garmtech.com/mcp"
    }
  }
}

If a client supports remote MCP but cannot complete MCP OAuth, use the local mcp-remote bridge (Node.js required):

{
  "mcpServers": {
    "garmtech": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://my.garmtech.com/mcp"]
    }
  }
}

The bridge opens the same GARMTECH sign-in page. Do not replace it with a permanent Bearer token.

Check the connection

1. Make sure the garmtech server is running or connected.
2. Ask the client to list your GARMTECH services.
3. Approve the tool call if the client asks for confirmation.
4. Before changing a hosting service, ask which capabilities are currently available.

Available operations depend on the selected account, service status, user permissions, ownership and the capabilities reported for that exact service.

Permissions and safety

The normal connection grants every client the same standard management access. The authorization page describes it in plain language and also lists the technical OAuth scopes. A connection does not bypass your account permissions, service ownership checks or the client's own confirmation prompts.

Command execution and short-lived control panel access are separate permissions and are switched off by default. Review the changes an AI client proposes before approving a write or delete operation.

Disconnect a client

Open My.GARMTECH → Services → MCP Connections, find the application and select Disconnect. Server-side access is revoked immediately. If you remove the server only inside the AI application, the authorization on the GARMTECH side may stay active.

Troubleshooting

• The browser did not open: open the client's MCP status screen and select Authenticate, Sign in or Start.
• 401 / authentication required: remove any manually added Authorization header and reconnect through OAuth.
• No tools appear: restart or refresh the MCP server after authorization.
• A tool is unavailable: ask for the capabilities of the exact service; unsupported operations are not exposed on purpose.
• Wrong client account: disconnect, reconnect and select the correct account during authorization.
• Still stuck: open a ticket with the client name and version, the exact error and the time it occurred; attach a screenshot if possible. Never include passwords or tokens.