Lists databases and tables, reads column definitions and keys, runs the SQL, and hands over the Play editor for follow-up digging.
6actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro runs a SQL query against ClickHouse and returns results. Your team pulls analytics, event logs, or metrics without external tools.
Ayro lists all available databases in the ClickHouse instance. Your team discovers what data is available for queries and troubleshooting.
Ayro enumerates tables within ClickHouse databases. Your team explores schema structure to build queries or verify data freshness.
Each card is one request a support team gets, and the ClickHouse actions Ayro runs to close it.
Ayro 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.
Ayro 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.
Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the ClickHouse actions it has and picks the ones a request needs.
Authorize the ClickHouse account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the ClickHouse actions that close it and chains as many as the request needs.
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 freeClickHouse · Ayro
What can you do in ClickHouse without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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.
All 6 actions your agent can call on ClickHouse, straight from the live MCP connection.
Execute a SQL query in ClickHouse and return the results.
Get comprehensive schema overview of an entire database including all tables and optionally their column definitions.
Get the ClickHouse Play web user interface for interactive query execution.
Get detailed schema information for a specific table including column definitions, types, keys, and optionally sample data.
List all databases in the ClickHouse instance.
List tables in ClickHouse databases.
Same connection, same setup. Pick the next one your team already uses.
Pulls the latest reading from every registered Ambient Weather station into the conversation.
Creates Databox data sources and datasets, pushes records into them, verifies each ingestion landed, and removes what is no longer feeding a dashboard.
Pulls clicks, impressions, and position data from a live property, inspects URLs that will not index, and submits or audits sitemaps.
Pulls survey responses for a form or report, resolves the fields behind them, and reports where and when a feedback form is shown.
Reads and updates trip status, starts and completes trips, maintains geofences and beacons, and turns partial addresses into verified coordinates.
Reads a receipt the moment it arrives, extracts merchant, totals, tax, and line items, and keeps the registries it matches against current.

Authorize the account and your agent has all 6 actions from the first conversation.
