Remote MCP server vs open-source MCP server
ClickHouse offers two MCP servers.
The remote MCP server provides the richest integration with ClickHouse Cloud, including service management, backup monitoring, ClickPipe visibility, and billing data, with no infrastructure to manage.
For self-hosted ClickHouse instances, see the open-source MCP server guides.
Enabling the remote MCP server
The remote MCP server must be enabled per service before it can accept connections. In the ClickHouse Cloud console, open your service, click the Connect button, select MCP, and enable it. For detailed steps with screenshots, see the setup guide.Endpoint
Once enabled, the remote MCP server is available at:Authentication
All access to the remote MCP server is authenticated via OAuth 2.0. When an MCP client connects for the first time, it initiates an OAuth flow that opens a browser window for the user to sign in with their ClickHouse Cloud credentials. Access is scoped to the organizations and services the authenticated user has permission to access. No additional API key configuration is required.Safety
All tools exposed by the remote MCP server are read-only. Each tool is annotated withreadOnlyHint: true in its MCP metadata. No tool can modify data, alter service configuration, or perform any destructive operation.