Is this an official ClickHouse MCP server?

No. It is Memtro's MCP server with Memtro's ClickHouse connector behind it: the connector reads ClickHouse through its API with the credentials you connect on Dashboard → Connections, and ClickHouse publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in ClickHouse?

Not yet. Today every ClickHouse tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Databases and warehouses

ClickHouse MCP server

ClickHouse in any MCP client, through Memtro: ClickHouse does not publish this server. Memtro's ClickHouse connector reads ClickHouse through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only SQL over ClickHouse (Cloud or self-hosted) via the HTTP interface: browse databases, tables and columns, then run SELECT queries with readonly=1, a 20s execution cap and at most 500 rows.

Reads

clickhouse_databasesList ClickHouse databases, or the tables in one database with engine, row count and size (largest first), optionally filtered by name.
clickhouse_schemaColumns of one ClickHouse table (name, type, default, codec hints, whether in the primary/sorting/partition key) with its engine, keys and row count…
clickhouse_queryRun a single read-only ClickHouse statement (SELECT / WITH, or SHOW / DESCRIBE / EXISTS).
clickhouse_explainEXPLAIN a read-only ClickHouse query without running it: plan (default) shows the query plan, estimate the parts/rows/marks it would read…

Connect it

First connect ClickHouse on Dashboard → Connections, then add Memtro to your client once. The ClickHouse tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared ClickHouse connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Which tables in the events database are the largest?
› How many page views per day in the last 14 days?
› What columns does analytics.sessions have?
› Top 10 countries by unique users this week
› Explain the plan for this query before I run it on the full table
› Average order value by hour yesterday

Questions

Is this an official ClickHouse MCP server?: No. It is Memtro's MCP server with Memtro's ClickHouse connector behind it: the connector reads ClickHouse through its API with the credentials you connect on Dashboard → Connections, and ClickHouse publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in ClickHouse?: Not yet. Today every ClickHouse tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.