Query schemas and run administration tasks across managed WaveHouse and ClickHouse projects.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Inspect callable tools, capabilities, and parameters exposed to AI agents by WaveHouse Cloud.
WaveHouse Cloud MCP server is intended for working with managed WaveHouse and ClickHouse projects through an MCP-based interface. The available listing describes two broad uses: querying project data and administering project resources. It identifies schema, queries, pipes, and policy as the supported areas.
Schema access can help an agent inspect the structure of a project before composing or reviewing a query. Query support covers interaction with project data, although the supplied material does not specify query syntax, result formats, or whether queries are read-only or can change data. Administration extends beyond data access to project-level resources and controls.
The listing specifically names pipes and policy alongside schemas and queries. A developer evaluating this server should therefore treat it as a fit for workflows that combine database inspection, query execution, and management of these WaveHouse or ClickHouse project features.
The WaveHouse Cloud MCP server is presented as the interface for managed WaveHouse and ClickHouse projects. Agents can use it to work with the supported project areas rather than interacting only with a static documentation source. The available description does not explain the transport, tool names, request parameters, response structure, authentication flow, or permission model.
A practical workflow could involve inspecting a schema, working with a query, and then handling related pipes or policy configuration. That sequence is an example of how the listed capabilities may fit together; the source does not document a required order or a specific end-to-end procedure.
Because the README is unavailable, implementation details should be verified before adoption. In particular, confirm which operations are exposed as tools, what permissions are required, and whether the same capabilities are available for both WaveHouse and ClickHouse projects.
The provided description supports these capability areas:
The listing does not provide individual tool names or state whether each area supports reading, writing, or both. Do not assume that a named capability implies unrestricted administration or access to every project resource.
No installation instructions, configuration fields, environment variables, authentication guidance, client compatibility information, or license details are included in the supplied material. The WaveHouse Cloud MCP server may require project-specific access, but the source does not state how that access is configured.
The description also does not define the distinction between WaveHouse and ClickHouse within the integration, document supported versions, or describe safety controls for queries and policy changes. Validate those details against the provider’s current documentation before connecting an agent to production projects. The available information establishes the server’s scope, but not its operational boundaries or deployment procedure.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/wavehouse-cloud)<a href="https://allmcps.com/mcp/wavehouse-cloud"><img src="https://allmcps.com/api/badge/wavehouse-cloud?style=directory" alt="WaveHouse Cloud on AllMCPs" /></a>