Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
AI-powered MCP server for Apache Druid cluster management and analytic
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
DRUID_ROUTER_URL, DRUID_COORDINATOR_URL, DRUID_AUTH_USERNAME, DRUID_AUTH_PASSWORD, DRUID_SSL_ENABLED, DRUID_SSL_SKIP_VERIFICATIONLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu terminal
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.1Completa los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
DRUID_COORDINATOR_URL envDRUID_AUTH_USERNAME envDRUID_SSL_ENABLED envDRUID_SSL_SKIP_VERIFICATION envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con el dominio iunera.com (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: DRUID_ROUTER_URL, DRUID_AUTH_PASSWORD
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (2.0.1) llegó al registro hace 2 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Excaliself
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
Solo se muestra el principio; lee el resto en el repo