Skip to main content

Compatible MCP clients

Claude
ChatGPT
Gemini
Cursor
Others
KmerHosting MCP works with these and other MCP-compatible clients. Use hosted OAuth when the client supports remote MCP servers, or local stdio when it launches the server on your machine.

Choose a connection mode

Recommended: use the hosted OAuth method when your AI client supports remote MCP. It avoids copying a long-lived API key into the client and provides a fast OAuth 2.1 + PKCE consent flow.

Hosted OAuth

Use https://mcp.kmerhosting.com/mcp with an MCP client that supports OAuth 2.1. Sign in to the KmerHosting Dash and approve only the scopes the client needs. The server publishes protected-resource metadata, authorization-server metadata, dynamic client registration, PKCE authorization, token refresh, and revocation. The consent screen exposes the public API scopes. If the requested selection includes infrastructure power, snapshots, root credentials, LXC reinstallation, or terminal access, the dash displays the concrete risks and requires a separate acknowledgement before issuing the authorization code. Keep only the scopes the MCP client needs; dangerous tool calls still require their own explicit confirmation.

Local stdio

Install the package and place the API key only in the MCP client environment:

Tool groups

Every mutating tool accepts an optional idempotencyKey. Destructive actions, root-password changes, reinstallations, terminal access, cancellation, and snapshot deletion/rollback require an explicit confirm: true value. Disabling LXC auto-renew and changing its billing period also require confirmation. Treat returned panel links and terminal tickets as secrets. Do not share them in prompts, logs, screenshots, or support messages.

AI-ready setup prompt

The Dash provides copy-ready variants for ChatGPT, Claude, Gemini, Cursor, and other MCP clients. This portable version contains the same authoritative setup context: