add ypipe MCP integration blueprints for ClickHouse, ClickHouse Playground, and chDB#200
Open
schmichri wants to merge 1 commit into
Open
add ypipe MCP integration blueprints for ClickHouse, ClickHouse Playground, and chDB#200schmichri wants to merge 1 commit into
schmichri wants to merge 1 commit into
Conversation
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First of all, thank you to the ClickHouse team and maintainers for your outstanding work! This MCP integration makes analytical queries and database exploration exceptionally fast and developer-friendly.
This Pull Request introduces the ypipe MCP integration blueprint configurations (
chdb.ypipe,clickhouseplayground.ypipe,localclickhouse.ypipe) for ClickHouse database integrations.What is ypipe?
ypipe is an AI agent orchestration and workflow automation platform. It supports declarative, one-click installations of MCP servers via Kubernetes-conforming YAML files called MCP Integration Blueprints.
How it works
These blueprints provide zero-setup and custom connection paths for ClickHouse:
chdb.ypipe: Boots an embedded ClickHouse engine (chDB) for analytical queries on local files (Parquet, CSV, JSON) and in-memory data viauv run mcp-clickhouse.clickhouseplayground.ypipe: Instantly provisions read-only access to ClickHouse's SQL Playground demo server without configuration.localclickhouse.ypipe: Exposes schema variables (CLICKHOUSE_HOST,CLICKHOUSE_PORT, etc.) allowing users to securely connect their own ClickHouse clusters.Adding these configurations makes it seamless for ypipe users to leverage ClickHouse databases within their agentic workflows. We are proud to support this integration!