Can this integration change data in ClickHouse, or only read it?

There is no dedicated insert, update, or DDL action in the toolkit - anything that writes would have to go through Execute ClickHouse Query. That means the privileges on the ClickHouse user you connect decide the answer: connect a read-only user and the integration is read-only.

How does Lyro avoid querying a column that does not exist?

It inspects the schema first. Get Table Schema returns column definitions, types, keys, and optionally sample data for one table, and Get Database Schema returns the whole database's structure in a single call, so the query is built from the real shape of the data.

What is the Play interface action for?

Get ClickHouse Play Interface returns ClickHouse's own web UI, an HTML page with a Monaco editor for writing and running queries. It is the handoff step: Lyro answers the immediate question, then gives an analyst the interactive surface instead of a screenshot of results.

What keeps an expensive query from hitting the cluster?

Two things worth setting up: List ClickHouse Tables reports each table's size and row count, so scope can be judged before a scan is run, and every query executes as the connected ClickHouse user, subject to whatever quotas and row limits are configured for that user in ClickHouse itself.

ClickHouse MCP integration

Lists databases and tables, reads column definitions and keys, runs the SQL, and hands over the Play editor for follow-up digging.

Connect ClickHouse See all integrations

6actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Execute clickhouse query
Lyro runs a SQL query against ClickHouse and returns results. Your team pulls analytics, event logs, or metrics without external tools.
List clickhouse databases
Lyro lists all available databases in the ClickHouse instance. Your team discovers what data is available for queries and troubleshooting.
List clickhouse tables
Lyro enumerates tables within ClickHouse databases. Your team explores schema structure to build queries or verify data freshness.

See all 6 actions

How businesses use ClickHouse + Lyro

Each card is one request a support team gets, and the ClickHouse actions Lyro runs to close it.

See what the instance holds before writing any SQL
Lyro lists the databases on the instance and the tables inside one, with each table's engine, size, and row count, so the right table is identified without someone opening a client to look.
List ClickHouse DatabasesList ClickHouse Tables
Read the structure of the table being queried
Lyro pulls a whole database's schema in one call, or a single table's column definitions, types, keys, and sample rows, so the query it composes matches the columns that actually exist.
Get Database SchemaGet Table Schema
Answer the question, then hand over the editor
Lyro runs the SQL and returns the result set, and when someone wants to keep exploring it returns the ClickHouse Play interface with its Monaco editor so they continue from the same query.
Execute ClickHouse QueryGet ClickHouse Play Interface

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the ClickHouse actions it has and picks the ones a request needs.

01
Connect ClickHouse
Authorize the ClickHouse account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the ClickHouse actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

ClickHouse · Lyro

Everything else about ClickHouse

Setup, permissions, and the limits of what Lyro can do inside ClickHouse.

There is no dedicated insert, update, or DDL action in the toolkit - anything that writes would have to go through Execute ClickHouse Query. That means the privileges on the ClickHouse user you connect decide the answer: connect a read-only user and the integration is read-only.

Every action available in ClickHouse

All 6 actions your agent can call on ClickHouse, straight from the live MCP connection.

Execute clickhouse query
Execute a SQL query in ClickHouse and return the results.
Get database schema
Get comprehensive schema overview of an entire database including all tables and optionally their column definitions.
Get clickhouse play interface
Get the ClickHouse Play web user interface for interactive query execution.
Get table schema
Get detailed schema information for a specific table including column definitions, types, keys, and optionally sample data.
List clickhouse databases
List all databases in the ClickHouse instance.
List clickhouse tables
List tables in ClickHouse databases.