Skip to content

feat(tools): Add ClickHouse support with querying and metadata retrieval #254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

shalevshalit
Copy link

  • Updated README to include ClickHouse as a supported datasource.
  • Implemented ClickHouse querying capabilities, including SQL execution, database and table listing, and table description.
  • Added integration and unit tests for ClickHouse functionalities.
  • Enhanced the disabled tools configuration to include ClickHouse options.

- Updated README to include ClickHouse as a supported datasource.
- Implemented ClickHouse querying capabilities, including SQL execution, database and table listing, and table description.
- Added integration and unit tests for ClickHouse functionalities.
- Enhanced the disabled tools configuration to include ClickHouse options.
@shalevshalit shalevshalit requested a review from a team as a code owner August 19, 2025 15:22
@CLAassistant
Copy link

CLAassistant commented Aug 19, 2025

CLA assistant check
All committers have signed the CLA.

@shalevshalit shalevshalit marked this pull request as draft August 19, 2025 15:59
@talshalom
Copy link

@shalevshalit - why embedding clickhouse capabilities in Grafana mcp, instead of using separate clickhouse mcp?

@shalevshalit
Copy link
Author

@talshalom same reason to use Prometheus or Loki.
The ability to query any grafana dashboard no matter what datasource you have.

@talshalom
Copy link

Loki & Prometheus are integral to Grafana, for example querying Loki can help an agent to iterate on errors when creating panels. With your approach "no matter what datasource", the Grafana mcp becomes "all datasources" mcp. I am not sure that is the intention, unless I missed the use case here. Why do you think using an embedded capabilities is better than using a standalone clickhouse mcp?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants