WaveHouse Cloud

cloud.wavehousePublished by wavehouse.cloudOfficial publisherv1.32.0Updated Nov 3, 2026

Browse, query, and administer your managed WaveHouse + ClickHouse projects (schema, pipes, policy).

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

Remote MCP endpoint for browsing, querying and administering managed WaveHouse and ClickHouse projects, including schema, pipes and policy.

What you can do
  • Browse and query managed WaveHouse and ClickHouse projects
  • Inspect and work with project schema
  • Manage pipes and policy settings
  • Administer projects through the hosted endpoint
When to use it
Useful when your ClickHouse or WaveHouse data lives in managed WaveHouse projects and you want an assistant to explore or administer them without a local setup.
Requirements
A remote streamable HTTP endpoint at mcp.wavehouse.cloud; OAuth authentication is required. No environment variables or headers are declared, and no local package is needed.
Before you install
The server can administer projects, so actions may change schema, pipes or policy; confirm before letting an assistant make changes. Access is granted through OAuth to your WaveHouse account, and queries and project data are handled by the hosted service.

Installation

In SourceWeft

  1. Open WaveHouse Cloud in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/cloud.wavehouse%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "wavehouse-cloud": {
      "type": "http",
      "url": "https://mcp.wavehouse.cloud/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

16
  1. v1.32.0LatestNov 3, 2026
  2. v1.31.0Oct 29, 2026
  3. v1.20.0Oct 26, 2026
  4. v1.19.0Oct 26, 2026
  5. v1.18.0Oct 25, 2026
  6. v1.14.0Oct 24, 2026
  7. v1.13.0Oct 22, 2026
  8. v1.9.0Oct 20, 2026
  9. v1.8.0Oct 20, 2026
  10. v1.7.0Oct 19, 2026
  11. v1.6.0Oct 15, 2026
  12. v1.5.0Oct 12, 2026
  13. v1.4.0Oct 10, 2026
  14. v1.3.0Oct 9, 2026
  15. v1.1.0Oct 4, 2026
  16. v1.0.2Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.