Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
AI-powered MCP server for Apache Druid cluster management and analytic
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
DRUID_ROUTER_URL, DRUID_COORDINATOR_URL, DRUID_AUTH_USERNAME, DRUID_AUTH_PASSWORD, DRUID_SSL_ENABLED, DRUID_SSL_SKIP_VERIFICATION「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"druid": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DRUID_ROUTER_URL",
"-e",
"DRUID_COORDINATOR_URL",
"-e",
"DRUID_AUTH_USERNAME",
"-e",
"DRUID_AUTH_PASSWORD",
"-e",
"DRUID_SSL_ENABLED",
"-e",
"DRUID_SSL_SKIP_VERIFICATION",
"docker.io/iunera/druid-mcp-server:2.0.1"
],
"env": {
"DRUID_ROUTER_URL": "your-value",
"DRUID_COORDINATOR_URL": "your-value",
"DRUID_AUTH_USERNAME": "your-value",
"DRUID_AUTH_PASSWORD": "your-value",
"DRUID_SSL_ENABLED": "your-value",
"DRUID_SSL_SKIP_VERIFICATION": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add druid --env DRUID_ROUTER_URL=your-value --env DRUID_COORDINATOR_URL=your-value --env DRUID_AUTH_USERNAME=your-value --env DRUID_AUTH_PASSWORD=your-value --env DRUID_SSL_ENABLED=your-value --env DRUID_SSL_SKIP_VERIFICATION=your-value -- docker run -i --rm -e DRUID_ROUTER_URL -e DRUID_COORDINATOR_URL -e DRUID_AUTH_USERNAME -e DRUID_AUTH_PASSWORD -e DRUID_SSL_ENABLED -e DRUID_SSL_SKIP_VERIFICATION docker.io/iunera/druid-mcp-server:2.0.1動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"druid": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DRUID_ROUTER_URL",
"-e",
"DRUID_COORDINATOR_URL",
"-e",
"DRUID_AUTH_USERNAME",
"-e",
"DRUID_AUTH_PASSWORD",
"-e",
"DRUID_SSL_ENABLED",
"-e",
"DRUID_SSL_SKIP_VERIFICATION",
"docker.io/iunera/druid-mcp-server:2.0.1"
],
"env": {
"DRUID_ROUTER_URL": "your-value",
"DRUID_COORDINATOR_URL": "your-value",
"DRUID_AUTH_USERNAME": "your-value",
"DRUID_AUTH_PASSWORD": "your-value",
"DRUID_SSL_ENABLED": "your-value",
"DRUID_SSL_SKIP_VERIFICATION": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"druid": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DRUID_ROUTER_URL",
"-e",
"DRUID_COORDINATOR_URL",
"-e",
"DRUID_AUTH_USERNAME",
"-e",
"DRUID_AUTH_PASSWORD",
"-e",
"DRUID_SSL_ENABLED",
"-e",
"DRUID_SSL_SKIP_VERIFICATION",
"docker.io/iunera/druid-mcp-server:2.0.1"
],
"env": {
"DRUID_ROUTER_URL": "your-value",
"DRUID_COORDINATOR_URL": "your-value",
"DRUID_AUTH_USERNAME": "your-value",
"DRUID_AUTH_PASSWORD": "your-value",
"DRUID_SSL_ENABLED": "your-value",
"DRUID_SSL_SKIP_VERIFICATION": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
DRUID_COORDINATOR_URL envDRUID_AUTH_USERNAME envDRUID_SSL_ENABLED envDRUID_SSL_SKIP_VERIFICATION envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名はドメイン iunera.com で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:DRUID_ROUTER_URL, DRUID_AUTH_PASSWORD
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(2.0.1)がレジストリに届いたのは2 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにDockerも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Excaliself
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find, read, create, edit, and organize Excalidraw drawings in your self-hosted Excaliself instance.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
A comprehensive Model Context Protocol (MCP) server for Apache Druid that provides extensive tools, resources, and prompts for managing and analyzing Druid clusters.
*Developed by iunera - Advanced AI and Data Analytics Solutions*
This MCP server implements a intend-based architecture where profiles picture their usaae intend and the corresponding area of Druid usage. The server provides three main types of MCP components:
Learn how to integrate AI agents with Apache Druid using the MCP server. This tutorial demonstrates time series data exploration, statistical analysis, and data ingestion using natural language with AI assistants like Claude, ChatGPT, and Gemini.
*Click the thumbnail above to watch the video on YouTube*
Experience your data like never before with [Y̊pipe (formerly Data-Philter)](https://ypipe.com), a local desktop application that makes offline AI practical, designed by iunera. It leverages this Druid MCP Server to provide a seamless, conversational interface for your Druid cluster.
*The easiest way to test iunera/druid-mcp-server is ypipe.com / https://github.com/iunera/ypipe*
For seamless integration, we provide a predefined Ypipe integration blueprint file:
This blueprint allows you to easily connect and configure the Druid MCP server in Ypipe through a visual workspace.
| Ypipe Workspace Flow | Druid Node Configuration |
|---|---|
When connected to an MCP client, you can inspect the available tools, resources, and prompts through the MCP inspector interface:
The tools interface shows all available Druid management functions organized by feature areas including data management, ingestion management, and monitoring & health.
The resources interface displays all accessible Druid data sources and metadata that can be retrieved through the MCP protocol.
The prompts interface shows all AI-assisted guidance templates available for various Druid management tasks and data analysis workflows.
A ready-to-use MCP configuration file is provided at mcp-servers-config.json that can be used with LLM clients to connect to this Druid MCP server.
The configuration includes multiple integration and transport options:
# STDIO mode (default)
docker run --rm -i \ -e DRUID_ROUTER_URL=http://your-druid-router:8888 \ -e DRUID_COORDINATOR_URL=http://your-druid-coordinator:8081 \ iunera/druid-mcp-server:latest
docker run -p 8080:8080 \ -e SPRING_PROFILES_ACTIVE=http,query \ -e DRUID_ROUTER_URL=http://your-druid-router:8888 \ -e DRUID_COORDINATOR_URL=http://your-druid-coordinator:8081 \ iunera/druid-mcp-server:latest
Note on Spring profiles:
# Build the application
mvn clean package -DskipTests
java -jar target/druid-mcp-server-2.0.1.jar
The server will start on port 8080 by default.
For detailed build instructions, testing, Docker setup, and development guidelines, see development.md.
DRUID_MCP_SECURITY_OAUTH2_ENABLED:true (OAuth2 is enabled by default as per the text above)false to disable OAuth2 authentication. When disabled, clients can access the server without providing OAuth2 tokens.If you prefer to use the pre-built JAR without building from source, you can download and run it directly from Maven Central.
Download the JAR from Maven Central https://repo.maven.apache.org/maven2/com/iunera/druid-mcp-server/
# STDIO mode (default)
java -jar target/druid-mcp-server-2.0.1.jar
java -Dspring.profiles.active=http \ -jar target/druid-mcp-server-2.0.1.jar
For detailed development information including build instructions, testing guidelines, architecture details, and contributing guidelines, see development.md.
The MCP server activates tools dynamically based on active Spring profiles (SPRING_PROFILES_ACTIVE). The default configuration runs the server in STDIO mode with the query profile enabled.
query (Default Active Profile)Provides safe, read-only data querying and browsing capabilities.
| Tool | Description | Parameters | Druid API Endpoint / Functionality |
|---|---|---|---|
getDatasources | List all available Apache Druid datasources or get detailed schema for a specific datasource. | datasourceName (String, optional), detailed (Boolean, optional) | /druid/v2/sql (queries system catalogs like INFORMATION_SCHEMA.TABLES & COLUMNS) |
getLookups | Get configuration or status of lookups for all or a specific tier. | tier (String, optional), lookupName (String, optional), includeStatus (Boolean, optional) | /druid/coordinator/v1/lookups/config & /status endpoints |
getSegments | Fetch segments metadata or details for a specific segment. | datasource (String, optional), segmentId (String, optional), detailed (Boolean, optional), metadataOnly (Boolean, optional) | /druid/coordinator/v1/datasources/{ds}/segments & system tables (sys.segments via /druid/v2/sql) |
getSegmentLoadQueue | Get the load queue status showing segments currently being loaded. | serverName (String, optional) | /druid/coordinator/v1/loadqueue |
queryDruidSql | Execute a SQL query against Druid datasources. | sqlQuery (String, required) | /druid/v2/sql (Router / Broker SQL endpoint) |
opsProvides administrative control over ingestion specs, tasks, streaming supervisors, retention rules, and compaction.
| Tool | Description | Parameters | Druid API Endpoint / Functionality |
|---|---|---|---|
getCompactionConfig | View compaction configuration or configuration change history for datasources. | datasource (String, optional), includeHistory (Boolean, optional) | /druid/coordinator/v1/config/compaction endpoints |
getCompactionStatus | Retrieve the current status of compaction runs and progress. | datasource (String, optional) | /druid/coordinator/v1/compaction/status |
manageCompaction | Add, update, or remove a compaction configuration. | action (Enum: UPSERT, DELETE, required), datasource (String, required), configJson (String, optional) | /druid/coordinator/v1/config/compaction (POST/DELETE) |
manageDatasourceOrSegment | Modify segment states or permanently drop a datasource. | action (Enum: ENABLE_SEGMENT, DISABLE_SEGMENT, KILL_DATASOURCE, required), datasource (String, required), segmentId (String, optional), interval (String, optional) | /druid/coordinator/v1/datasources & segment POST/DELETE |
manageLookup | Create, update, or delete a lookup configuration. | action (Enum: UPSERT, DELETE, required), tier (String, required), lookupName (String, required), configJson (String, optional) | /druid/coordinator/v1/lookups/config (POST/DELETE) |
queryDruidMultiStage | Execute a multi-stage SQL query (MSQ) against Druid datasources as a task. | sqlQuery (String, required) | /druid/v2/sql/task (MSQ execution endpoint) |
queryDruidMultiStageWithContext | Execute a multi-stage SQL query with custom context parameters. | sqlQuery (String, required), contextJson (String, optional) | /druid/v2/sql/task with context configurations |
getMultiStageQueryTaskStatus | Get the status of a multi-stage query task. | taskId (String, required) | /druid/indexer/v1/task/{taskId}/status |
cancelMultiStageQueryTask | Cancel a running multi-stage query task. | taskId (String, required) | /druid/indexer/v1/task/{taskId}/shutdown (POST) |
| getRetentionRules | Retrieve retention rules or audit history for a specific datasource or all datasources. | datasource (String, optional), includeHistory (Boolean, optional) | `/druid/co
冒頭だけを表示しています。続きはリポジトリで読めます