Enable and connect ClickHouse Cloud Remote MCP Server
This guide shows you how to enable the ClickHouse Cloud Remote MCP Server and set it up for use with common developer tools.
Prerequisites
- A running ClickHouse Cloud service
- Your IDE or agentic development tool of choice
Enable remote MCP server for Cloud
Connect to the ClickHouse Cloud service for which you want to enable remote MCP server, click on the Connect button in the left hand menu.
A box with connection details will open.
Select "Connect with MCP":
Toggle the button on to enable MCP for the service:
Copy the displayed URL, which is the same as the one below:
Setup remote MCP for development
Choose your IDE or tool below and follow the corresponding setup instructions.
Claude Code
From your working directory, run the following command to add the ClickHouse Cloud MCP Server configuration to Claude Code:
Then launch Claude Code:
Run the following command to list MCP servers:
Select clickhouse-cloud and authenticate via OAuth using your credentials for ClickHouse Cloud.
Claude web UI
- Navigate to Customize > Connectors
- Click the "+" icon and Add custom connector
- Give the custom connector a name like
clickhouse-cloudand add it - Click the newly added
clickhouse-cloudconnector and click Connect - Authenticate using your ClickHouse Cloud credentials via OAuth
Cursor
- Browse and install MCP servers from the Cursor Marketplace.
- Search for ClickHouse and click "Add to Cursor" on any server to install it
- Authenticate with OAuth.
Visual Studio Code
Add the following configuration to your .vscode/mcp.json:
For more details refer to the Visual Studio Code docs
Windsurf
Edit your mcp_config.json file with the following config:
For more details refer to the Windsurf docs
Zed
Add ClickHouse as a custom server. Add the following to your Zed settings under context_servers:
Zed should then prompt you to authenticate via OAuth when it first connects to the server. For more details refer to the Zed docs
Codex
Run the following command to add the ClickHouse Cloud MCP server via the CLI: